Skip to content
This repository has been archived by the owner on Aug 25, 2024. It is now read-only.

feat: gateway jwt auth supports revoked tokens #106

Merged
merged 8 commits into from
Jul 18, 2024

Conversation

nicoloboschi
Copy link
Collaborator

@nicoloboschi nicoloboschi commented Jul 12, 2024

New config inside the jwt config revoked-tokens-store to configure to an s3 bucket.

provider: jwt
configuration:
  auth-claim: xx
  revoked-tokens-store:
    type: s3
    refresh-period-seconds: 30
    configuration: 
     s3-bucket: xx
     s3-object: xx
     s3-access-key: xx
     s3-secret-key: xx

I've also made all the jwt config kebab case
Currently only implemented for jwt but it's easy to extend to others.

Note that if the bucket or object doesn't exist, the auth works normally.
The object must be in format:

token1
token2
token3
... 

@nicoloboschi nicoloboschi merged commit abd8bc9 into vectorize-io:main Jul 18, 2024
8 of 11 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant