Activating the IDP
Hello,
Currently we were using
https://zitadel.com/docs/apis/resources/admin/admin-service-add-idp-to-login-policy
to activate the IDP that is created, this was working foe us initially .
Now after creating the IDP using: https://zitadel.com/docs/apis/resources/admin/admin-service-add-google-provider
we use the to activate the idp , but this is not activating the IDP now.
Can you please suggest if the API behaviour is changes or what should we do in order to activate the idp using API after it is activated.
ZITADEL Docs
Add/link a pre-configured identity provider to the login settings of the instance. This means that it will be shown to the users on the login page. It affects all organizations, without custom login settings.
ZITADEL Docs
Add Google Identity Provider
11 Replies
Also to add to this, we have the default ZITADEL org and a org that we created.
So on calling https://zitadel.com/docs/apis/resources/admin/admin-service-add-idp-to-login-policy
when we use the above endpoint, the IDP is activated in the ZITADEL org and is not activated in the org that we have created?
is this the excpected behaviour, because earlier this was not happening liek this, IDP's were active accross organizations
ZITADEL Docs
Add/link a pre-configured identity provider to the login settings of the instance. This means that it will be shown to the users on the login page. It affects all organizations, without custom login settings.
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
@Zitadel Staff @fabienne , Awaiting a response on this 🙂
Hi @2isprime, as you may know the discord is normally used in the community, if there are bugs or unexpected/change behaviour please create an issue https://github.com/zitadel/zitadel/issues if you not already have. Nonetheless, give me some time to have a look and maybe explain this situation or figure out if something went wrong.
GitHub
Issues · zitadel/zitadel
ZITADEL - Identity infrastructure, simplified for you. - Issues · zitadel/zitadel
And please refrain from marking ZITADEL Staff, as this discord is used as a community hub.
@2isprime @mohit-actualize Did you change anything else on the login policy on an organizational level?
@stebenz , no changes were made to the login policy
Which means that you see no such button on the organization which now has the IDP not activated?
"Reset to instance default" is the button that is meant here
@2isprime
@stebenz , I do see this button in the organization in which the IDP was not activated.
Is there any specific policy change to be done to get the IDP activated?
So the situation is as follows, if you activate the IDP on instance level, than that is the default used for all organizations, if you then change the login policy on an organization level, then this settings overwrites the default (the actived IDPs belong to the login policy).
You either have to restore the instance default and customize your settings on instance level if that's possible, or you have to customize your settings on organization level and just activate the IDP there.
thanks, will check this .