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

Authorization: Bearer eyJ0eXAiOiJKV1QiLC...not the same as the access_token inserted in database #22

Closed
nicolasflorth opened this issue Aug 2, 2018 · 1 comment

Comments

@nicolasflorth
Copy link

Can you explain please, why Authorization: Bearer eyJ0eXAiOiJKV1QiLC is not the same as access token inserted into database?
Database value is 28fbf5feb43f5ddb2c559d26213304612366a2680f5e47be8e544430a4eb9a133c88a03a24f8189a

@moeen-basra
Copy link
Owner

you can check this article for basic understanding, how jwt actually get created.

https://medium.com/vandium-software/5-easy-steps-to-understanding-json-web-tokens-jwt-1164c0adfcec

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