Has anyone had any luck hosting Omni with Zitadel as the SAML provider? #1072
Replies: 1 comment
-
I've determined the cause. Omni is pulling the I'm a bit confused as to why it isn't simply pulling the email from the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've been trying self host an instance of Omni using Zitadel as the identity provider and am stuck at this point. The actual XML it generates seems correct and even gets as far as Omni prompting me to issue keys to the user (who's name is correct as well) (on Omni's Authenticate UI Access) but upon clicking the "Log In" button, nothing visibly happens, nor does anything appear in the docker-compose logs.
In the browser console an error occurs with the following: "Error generating keypair: Invalid user ID format." Looking at the data Omni receives via docker-compose's log function, shows that the field userID is what it should be so I'm not sure if that's the same user ID that the error is referring to or not.
The XML config in Zitadel looks like this:
And the
--auth-saml-url=
in Omni'sconfig.env
file points to:https://id.example2.com/saml/v2/SSO
. I've tried a number of different endpoints includinghttps://id.example2.com
on it's own,https://id.example2.com/saml/v2/metadata
in an attempt to point towards the metadata, andhttps://id.example2.com/saml/v2/certificate
to point towards it's IDP cert.I'm at the point where I'm entirely out of ideas, so I'm hoping someone here might know what's going wrong. If anyone can point me in the right direction, I would really appreciate it.
Beta Was this translation helpful? Give feedback.
All reactions