Skip to content
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

Router problem #13

Open
markjovis opened this issue Aug 5, 2016 · 1 comment
Open

Router problem #13

markjovis opened this issue Aug 5, 2016 · 1 comment

Comments

@markjovis
Copy link

markjovis commented Aug 5, 2016

It works using the old "@angular/router-deprecated" module, but it doesn't work when using the new "@angular/router". Basically, with the new router module, after the user successfully authenticates the angular2-adal appears to interpret the returned token from Azure AD as a route which obviously errors out with a no match route error. Is there a way to make this work with the new route module? If not, is there a work around for this? I don't want to create my app using the old route library which doesn't look like it'll stay around much longer.

@fume
Copy link

fume commented Nov 9, 2016

You should activate the hash mode in the New router. https://angular.io/docs/ts/latest/guide/router.html#!#browser-url-styles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants