Your Azure AD instance must be configured to redirect any authentication request back to redirect.html
upon successful authentication. redirect.html
will handle sending the authenticated user to their intended destination.
For example, if an unauthenticated user navigates to "myapp.example/deep/link/to/somewhere/in/your/app", they will be taken through the normal Azure AD login process, sent to redirect.html
, then properly routed to the deep link in your app.
You're welcome!
The intended behavior is that
id_token
is in the URL (as the hash) when going toredirect.html
, but theadal
plugin should then strip it out and redirect to wherever your user was originally going. If you're saying that you see theid_token
in your final URL likemy.app/users/1#id_token=...
, then you may want to debug throughredirect.html
and see if theif
is necessary, sinceid_token
is part oflocation.hash
.