-
Notifications
You must be signed in to change notification settings - Fork 436
Replies: 2 comments · 3 replies
-
Tagging @livio-a and @stebenz since you where engaged with this error already. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I have a similar issue. We built our own Login UI and allow the users to login with external IDPs. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hm, you do self-host zitadel I guess, right. What happen if you start zitadel with a debug log level and try again? |
Beta Was this translation helpful? Give feedback.
All reactions
-
For my environment, I'd defined these environment variables:
Restarted the Zitadel pod; and performed a login via our SAML IdP, with the logs below. I did not see the HTTP 400 Bad Request in the logs though.
|
Beta Was this translation helpful? Give feedback.
All reactions
-
@schlapzz, have you found how to fix Apple sign-in issue? I have the similar issue with native apple sign-in |
Beta Was this translation helpful? Give feedback.
-
Zitadel Version: v2.49.1
Environment: Self-hosted
Hi, we have configured a SAML SP in Zitadel to use our internal in-house SAML IdP as the identity source.
After configuring the SAML SP, the Zitadel login page shows the link of the configured SAML SP, and clicking on it redirects to our internal IdP's login page. That's all good. But after authenticating with our IdP, the browser is redirected to a page that auto POST to Zitadel's
/idps/<idp-id>/saml/acs
endpoint, and that's when we get a HTTP 400 Bad Request and the text "ID=IDP-Hk38e Message=Errors.Intent.NotStarted" back from Zitadel.My questions are:
Beta Was this translation helpful? Give feedback.
All reactions