1

I'm unable to customize the authorisation callback URL to my custom domain when adding a new SAML provider in Google Cloud Identity platform. I took the following steps:

  • I successfully connected my domain via the firebase console: the status says 'Connected', and the SSL certificate has been provisioned.
  • In Identity Platform, I added my custom domain to the authorized domains on the project level.
  • I'm trying to add a SAML provider for a tenant.

I cannot edit the callback url in the cloud console. Also, when adding the provider with a custom url via a client SDK, the provider is created, but again with the default url.

Any pointers?

From the documentation:

enter image description here

sdcbr
  • 7,021
  • 3
  • 27
  • 44

1 Answers1

3

This is expected.

The real issue is that the docs give the understanding of changing the callback URL in the console but you should change the authDomain in your code rather than in the GCP console and when making the request, you will see the callback URL using your custom domain.

For example, if in your code you have:

const config = {
  apiKey: "dsfdsDSSDDSFSDfsdf5ds14f5s",
  authDomain: "PROJECT_ID.firebaseapp.com",
};

You only have to change the authDomain for example to:

const config = {
  apiKey: "dsfdsDSSDDSFSDfsdf5ds14f5s",
  authDomain: "login.mydomain.com",
};

The only condition to make this work is that the domain you want to use is in the Authorized domains.

Puteri
  • 3,348
  • 4
  • 12
  • 27
  • Really? Wow, the documentation is really off then? – sdcbr Nov 03 '20 at 09:28
  • Yes, really hehe. Please check if this works for you and if so, you can accept the answer c: – Puteri Nov 03 '20 at 13:25
  • I think its because the instructions are generic for multiple providers, at least some of which do likely have the callback URL as part of the console settings. The Google provider and custom SAML providers (and perhaps others) do not, and it would be nice if the docs called that out. – Raman Jun 03 '21 at 14:44