-
Notifications
You must be signed in to change notification settings - Fork 184
Open
Description
I'm submitting a...
- Regression (a behavior that used to work and stopped working in a new release)
- Bug report
Current behavior
Sign in is successful, AngularTokenService.userSignedIn() returns '401 Unauthorized'.
CanActivate [AngularTokenService] returns nothing.
Expected behavior
I'm expecting token validation, given sign in was successful.
What is the motivation / use case for changing the behavior?
I'm restricting a component using CanActivate. I'm want to access this restricted component.
Environment
Angular-Token version: 7.0.1
Angular version: 10.0.0
Bundler
- Angular CLI (Webpack)
Browser:
- Chrome (MacOS Mojave) version 90.0.4430.212
matheuschvs
Metadata
Metadata
Assignees
Labels
No labels