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

inject secret for jwt at deployment #7

Closed
volodymyrss opened this issue Feb 23, 2021 · 2 comments
Closed

inject secret for jwt at deployment #7

volodymyrss opened this issue Feb 23, 2021 · 2 comments
Assignees
Milestone

Comments

@volodymyrss
Copy link
Member

No description provided.

@burnout87
Copy link

burnout87 commented Mar 12, 2021

Does this imply that the same secret will be used for the encoding of the token across all users?

And, taking a look at the configuration of the frontend (here) the secret can be stored within the DB

@volodymyrss
Copy link
Member Author

Yes, in a given platform deployment, one secret can be used for specific communication channel.
we could also use it both for API and frontend since they work in the same way.

Technically token is not encoded with secret, it is signed.
Token itself is encoded with base64 - you can also just decode it with bas64 module.
Or you can decode it with pyjwt and not verify. at least as an option - also for tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants