You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what you want to accomplish.
Hi, we have a configuration where we serve an angular web app with hash routing. We are observing that once we authenticate using Azure or Google as a provider after successful authentication the redirect goes to the original path but stops at the hash sign and does not auto route the home page we expect. If we manually type home page after the hash /#/ we will get to the page. I noticed 'enable js redirect' and tried it but as yet no difference in behaviour. Do we need to set a after login redirect manually ? Any advice appreciated thank you
The text was updated successfully, but these errors were encountered:
Hi, we have a configuration where we serve an angular web app with hash routing. We are observing that once we authenticate using Azure or Google as a provider after successful authentication the redirect goes to the original path but stops at the hash sign and does not auto route the home page we expect. If we manually type home page after the hash /#/ we will get to the page. I noticed 'enable js redirect' and tried it but as yet no difference in behaviour. Do we need to set a after login redirect manually ? Any advice appreciated thank you
The text was updated successfully, but these errors were encountered: