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

Tokens are not verified with CKAN_OAUTH2_JWT_ENABLE=true #37

Open
pazepaze opened this issue Jul 3, 2020 · 0 comments
Open

Tokens are not verified with CKAN_OAUTH2_JWT_ENABLE=true #37

pazepaze opened this issue Jul 3, 2020 · 0 comments

Comments

@pazepaze
Copy link

pazepaze commented Jul 3, 2020

When jwt is enabled via env/config, tokens are accepted without verification. I tested this with expired but otherwise valid tokens. The token is decoded with jwt.decode(access_token, verify=False). As far as I understand, this means that any token would be accepted, since the signature is not checked with a public key/certificate.

So you could just change the username in the token and sign it with an arbitrary key to impersonate any user.

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

1 participant