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

[FEAT]: Use PKCE OAuth flow #14

Open
gamemaker1 opened this issue Mar 22, 2021 · 0 comments
Open

[FEAT]: Use PKCE OAuth flow #14

gamemaker1 opened this issue Mar 22, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request oauth Issues related to OAuth 2.0 used to access user's cloud storage

Comments

@gamemaker1
Copy link
Member

Is your feature request related to a problem? Please describe.

Currently to setup an account, you need to create an app with your own Google/Microsoft account and get the client ID, secret, then authorize the app. It would be less of a hassle for users if all they needed to do was to authorize the app.

Describe the solution you'd like

Use PKCE OAuth flow (supported by Google, Microsoft, Dropbox, etc) to get an access token.

Describe alternatives you've considered

The less secure alternative is embedding the client secret into the CLI itself.

Additional context

Add any other context or screenshots about the feature request here.

@gamemaker1 gamemaker1 transferred this issue from dabbu-knowledge-platform/files-api-server Mar 22, 2021
@gamemaker1 gamemaker1 added enhancement New feature or request oauth Issues related to OAuth 2.0 used to access user's cloud storage labels Mar 22, 2021
@gamemaker1 gamemaker1 self-assigned this Mar 22, 2021
@gamemaker1 gamemaker1 added this to To do in Issue progress May 25, 2021
@gamemaker1 gamemaker1 removed this from To do in Issue progress May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request oauth Issues related to OAuth 2.0 used to access user's cloud storage
Projects
None yet
Development

No branches or pull requests

1 participant