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

Change the tf/task jwt token management #27

Merged
merged 4 commits into from
May 17, 2024
Merged

Change the tf/task jwt token management #27

merged 4 commits into from
May 17, 2024

Conversation

isaaguilar
Copy link
Contributor

Writes jwt tokens to a secret and sourced into a task. JWTs now come with single use refresh token. A new login endpoint is used to refresh tokens @ /refresh

Writes jwt tokens to a secret and sourced into a task. JWTs now come with single use refresh token. A new login endpoint is used to refresh tokens @ `/refresh`
From personal experience, its more common for k8s networking to fail than database entries to fail. For this reason, the k8s secret updater is moved before modifying the database. Either way, this change is not the best solution to handle failure sceanrios, but it's "good enough".
@isaaguilar isaaguilar merged commit fba2a73 into master May 17, 2024
1 check passed
@isaaguilar isaaguilar deleted the refresh-token branch May 17, 2024 02:02
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

Successfully merging this pull request may close these issues.

1 participant