adorable-camera-99335
04/13/2023, 7:55 AMhttps://<slug>.<http://projects.oryapis.com/self-service/methods/oidc/callback/<providerId|projects.oryapis.com/self-service/methods/oidc/callback/<providerId>>
When attempting to replace it with our custom domain (<https://auth>.<domain>.com/self-service/methods/oidc/callback/<providerId>
) the request obviously fails with 400: redirect_uri_mismatch
.
Is it somehow possible to replace the redirect URI with the custom domain?
There are multiple reasons why this is important for us:
⢠We are serving cautious B2B customers. Whitelisting arbitrary domains like <slug>.<http://projects.oryapis.com|projects.oryapis.com>
on their networks is a no-go for them when integrating our service. They want to have a clear list of subdomains which we control.
⢠Those B2B customers have to go through a setup process with us. Its weird we have to tell them they have to allow the redirect URI from oryapis.com in their OIDC setup. We'd rather have them allow a subdomain from us.
⢠Its confusing for the users; e.g. when going with Google OIDC, its written "Continue to oryapis.com" instead of our domain, which would be much clearer.
Thank you š
cc: @mysterious-processor-51766high-optician-2097
ory patch identity-config <project-id> \
--add '/selfservice/methods/oidc/config/base_redirect_uri="<https://your-custom-domain/>'
high-optician-2097
adorable-camera-99335
04/13/2023, 8:05 AMvalue for /services/identity/config/selfservice/methods/oidc/config/base_redirect_uri must be valid JSON but got: <https://auth.domain.com/>
My command:
ory patch identity-config project-slug-foobar --add '/selfservice/methods/oidc/config/base_redirect_uri="<https://auth.domain.com/>"'
mysterious-processor-51766
04/13/2023, 8:06 AMadorable-camera-99335
04/13/2023, 8:16 AM