We have configured Google and MS as external IDP, but these buttons do now show up at login
What setting are we missing? We setup all client_id's and secrets for both.
3 Replies
Hi @Riël, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. [Configure Google as an Identity Provider in ZITADEL] (1) :
This covers the complete Google IDP configuration process including activation and login policy settings.
2. [Google IDP not visible in login page] (2) :
This discusses troubleshooting when Google IDP buttons don't appear, including organization-level vs instance-level configuration.
To learn more, see the sources I considered:
[1] Configure Google as an Identity Provider in ZITADEL
[2] Google IDP not visible in login page
Feel free to tag @Ask Inkeep with additional questions.
Thanks found it.
It is indeed the urn:xxx scope that is needed because we do this organisational level.
I don't really understand why: because of the connected app we try to authenticate to, there is a client_id that is already scoped to a specific organisation.
Glad I could be helpful. Feel free to create a new thread with any new questions you may have.