Cannot log in when {useHash: true} is used in RouterModule.forRoot() with Angular 2

[stefanruijsenaars]

This is likely a JWT issue, but crossposting to this issue queue in case others run into this issue (see auth0/angular2-jwt#211)

[luisrudge]

Hi @stefanruijsenaars - the problem is that angular-router clears the hash (angular/angular#6595) you're receiving from Auth0. We added the possibility to prevent Lock from parsing the hash when it is instantiated and resuming the authentication workflow in #790. However, this was not released yet. There's a workaround you can use in the meantime: auth0-samples/auth0-angularjs2-systemjs-sample#40 (comment).

With that being said, next version is scheduled to be released in the next week and we'll have angular examples you can follow.
Thanks!

[stefanruijsenaars]

thank you!

…

On 13 January 2017 at 06:48, Luís Rudge ***@***.***> wrote: Hi @stefanruijsenaars <https://github.com/stefanruijsenaars> - the problem is that angular-router clears the hash (angular/angular#6595 <angular/angular#6595>) you're receiving from Auth0. We added the possibility to prevent Lock from parsing the hash when it is instantiated and resuming the authentication workflow in #790 <#790>. However, this was not released yet. There's a workaround you can use in the meantime: auth0-samples/auth0-angularjs2-systemjs-sample#40 (comment) <auth0-samples/auth0-angularjs2-systemjs-sample#40 (comment)> . With that being said, next version is scheduled to be released next week and we'll have angular examples you can follow. Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#806 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEuI7jEeU0INe-PObOhhUUJHUvR7mCM1ks5rR47ZgaJpZM4LijoB> .