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.

Sign up for GitHub

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

Jump to bottom

UserSignedIn Returns '401 Unauthorized' #545

Open
4 tasks done
masscreation opened this issue May 16, 2021 · 0 comments
Open
4 tasks done

UserSignedIn Returns '401 Unauthorized' #545

masscreation opened this issue May 16, 2021 · 0 comments

Comments

@masscreation
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@masscreation