Outage information
Possible to activate user over console UI?
ZOHO external IDP using generic OIDC
Zitadel - Facing issue while changing the logo
OIDC callback url when using custom login, doesn't use custom domain
{CUSTOM_DOMAIN}/ui/login/login/externalidp/callback
(and in that case it actually does use the custom domain). But when the request goes out it actually sets the callback to a path {GIVEN_ZITADEL_CLOUD_DOMAIN}/idps/callback
.
We can make this work, but it would be nice to have our clients configuring their SSO with the custom domain we have setup instead....Userinfo endpoint not returning all roles from all Role Audiences
openid profile email
urn:zitadel:iam:org:project:id:zitadel:aud
urn:zitadel:iam:org:project:id:<PROJECT-ID-1>:aud
...Device Authorization with Okta using zitadel/oidc
zitadel/oidc
for device authorization against Okta, but I'm getting back this error from DeviceAuthorization
:
ErrorType=invalid_request Description=The client_assertion_type is invalid.
ErrorType=invalid_request Description=The client_assertion_type is invalid.
Is there a way to have multiple microsoft identity provider but just 1 button instead of x buttons
Is there a way to only allow a user to manage project permission grants instead of project owner?
Assistance Needed: Google IDP Integration in ZITADEL Login
v2beta/actions/* 404 with Actions V2 feature enabled
/v3alpha/actions/*
endpoints and I went to switch to v2beta
, but it seems all of the endpoints return 404:
```...
Is there a proto maven/gradle package?
Login shows Social idP, but not on Registration screen

K8s (with traefik) error 400 or 500
Migrating from CRDB to PGSQL
Disabling MFA globally

Roles missing in access token (JWT)
Debugging token handshake
Initate Login URI from SSO provider
Initate Login URI
configuration variable that I don't know what to tell them to put in. For reference, when specified and the client then tries to start the login, they are redirected to the configured URI with an iss
search param that refers back to the cleints SSO provider. I assume at that point the app just needs to redirect to that issuer the same way the redirection happens if the user were to click the SSO button on our login page.
I've attached a picture of the configration options within Okta....