Workforce Identity Federation with OIDC to support Google

Today I tried to set up OIDC for Workforce and grant access to the database using my IdP (Google), but the current implementation doesn’t support ClientID + Client Secret and when using Google as IdP we must use both, otherwise the flow won’t work properly. I know that there are other IdPs that support that, some of them are listed in the official Atlas docs, but changing IdP is not an option and Google is big enough to be supported by an important feature like this one.

3 Likes

I have the same case. Do you have news about that?