We have multiple applications under a single tenant, and want to take advantage of the Universal Login. What is confusing that there are multiple places where the redirect URI can be configured, and according to the docs, Auth0 will redirect back to the calling application (mentioned universal-vs-embedded-login). This is not occurring though as expected. If we specify that a SAML enterprise connection should be used. It seems that the redirect URI for that SAML connection takes precedence, even though the calling application specified a redirect uri in the URL when hitting the Universal login. Is there something I am missing, or maybe a recommended alternative configuration? To summarize, when running locally (even with an https proxy ) we access the Universal login endpoint for the tenant with the client_id of the application, the redirect_uri, and the SAML enterprise connection to use. Once logged in, the redirect_uri is ignored (provided in he URl) and redirects back to the what is provided by the enterprise connection.
Hi @tallen1,
Welcome to the Auth0 Community!
The login redirect_uri will be reached after the authentication process has been finalized on the Universal Login. The SAML connection’s redirect_uri should be https://{yourDomain}/login/callback?connection={yourConnectionName}. This will redirect you back to the Universal Login page to continue and finalize the authentication process after which you will be redirected to the desired URI.
If you have any other question for us feel free to reach out.
Have a good one,
Vlad
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.