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

Per-user GITHUB_ACCESS_TOKEN #392

Open
suculent opened this issue May 16, 2022 · 1 comment
Open

Per-user GITHUB_ACCESS_TOKEN #392

suculent opened this issue May 16, 2022 · 1 comment
Assignees
Labels
Milestone

Comments

@suculent
Copy link
Owner

ENV var in tests.

Otherwise, User should be able to insert/update his access token somewhere in Profile screen.

Upon entering, token is validated with GitHub and used to push first available RSA key to GitHub. If key is not available, it will be created.

So entering GHAT (github access token) ensures communication with GitHub without creating RSA Key manually (this remains for other GITs).

@suculent suculent added this to To do in THiNX Device API via automation May 16, 2022
@suculent suculent added this to the UI+JWT milestone May 16, 2022
@suculent
Copy link
Owner Author

suculent commented Feb 20, 2023

Added, unit-tested, just not integrated yet. The token storage should be Vault.

@suculent suculent changed the title Allow specifying GITHUB_ACCESS_TOKEN Per-user GITHUB_ACCESS_TOKEN Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants