-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPA - unable to complete authentication from another route #316
Comments
if |
I couldn't get the hashtag to work in my Azure Angular 5 app either. I had to take out the |
@dougmolineux There is an issue with angular library itself for hashbang urls. angular/angular#16710 |
Closing this issue as the original issue seems to be resolved. |
I still have this problem when using useHash: true. Seemingly this issue cannot fix in angular 6 and more :( |
I have a SPA with Aurelia, and configured it with MSAL.
When I load app from the base route http://localhost:8080 it authenticates user, then redirects to homepage and am able to get the logged in User and display it on navbar.
When I load from another route, like http://localhost:8080/#/counter, it authenticates user, redirecters to counter page, but getUser() returns null.
Is there something I'm missing that would prevent authentication from completing on a different route?
Sample Repository:
https://github.com/jbockle/aurelia-azure-active-directory
The text was updated successfully, but these errors were encountered: