Skip to content

Add a secret to the AccessToken#389

Draft
arteymix wants to merge 1 commit intodevelopmentfrom
feature-secret-for-access-token
Draft

Add a secret to the AccessToken#389
arteymix wants to merge 1 commit intodevelopmentfrom
feature-secret-for-access-token

Conversation

@arteymix
Copy link
Member

@arteymix arteymix commented Aug 25, 2023

The bearer authentication now accepts a {token}:{secret} syntax similar to basic authentication. The secret part is optional to be backward-compatible with existing access tokens.

  • adjust token-based authentication to accept an optional secret
  • add some tests for pre-1.6 tokens without secrets
  • add a warning that access token without secret should be revoked and regenerated
  • display the secret once when the access token is created
  • display the secret once when a service account is created (it get an initial access token)

@arteymix arteymix force-pushed the feature-secret-for-access-token branch from 43c0cd0 to 3e6ba6f Compare August 26, 2023 08:03
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