Problems when token is not existing
See original GitHub issueI have faced an issue when sendAccessToken: true
is set and use ri snot logged (he not suppose to be logged in all pages) requests header is set anyway Authorization: Bearer null
this causes error 500 when used with .NET CORE 2 Authorization attribute.
I think it will be good to not send token if it has no value even when this flag is set. For now i will stick with my own version of intercpetor
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
"token does not exist" - Stack Overflow
It happen because the authentication token of CLI does not match with our accounts. Solution: Try running ask init command again. And If...
Read more >I'm Having Problems with My Hardware Token for Two-Step ...
Solution: You can fix the token by logging in with a passcode generated by the token three times in a row. At the...
Read more >Solved: Access Token Information Not Working - 382648
The existing Access Token Endpoint that's referenced within our documentation is only configured to work with our old authorization management ...
Read more >Token is not authorized immediately - Auth0 Community
I'm using auth0 in a spring boot application (micro services architecture) with security. One of the micro services in my application logs ...
Read more >Generate access token, if Refresh token not exist - Drupal
Problem /Motivation The existing code only automatically replaces an expired token if a refresh token is provided.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@liranAtli Aye, this was fixed around May 10th I think, the relevant line of code (AFAICT) is here. You might need to upgrade to the latest release (and Angular 6 as such), or backport it yourself (since the 3.x version doesn’t have the check).
Hi, Some one can tell me if this problem is solved yet? or any suggest for solution 😃