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

Encrypt Token #353

Open
alejcas opened this issue Nov 7, 2019 · 1 comment
Open

Encrypt Token #353

alejcas opened this issue Nov 7, 2019 · 1 comment
Assignees

Comments

@alejcas
Copy link
Member

alejcas commented Nov 7, 2019

We should by default (but configurable) encrypt and decrypt the token info.

This will be a task done by the TokenBackend chosen.
The default BaseTokenBackend should implement an option to encrypt that will be active by default.

The option can be passed from the Account to the Connection to finally end at the TokenBackend.

The key to decrypt and encrypt should be configurable but with a default (maybe the client_secret can be the default key to the encryption?

This will maybe add another requirement to this library.
Maybe this should be only an example of a Custom BaseTokenBackend like a SecureBaseTokenBackend but I feel kind of obliget to include this as a default.

@alejcas alejcas self-assigned this Nov 7, 2019
@Ashesh3
Copy link

Ashesh3 commented May 29, 2020

+1 looking to encrypt the token file somehow

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