splunk / splunk/vault-plugin-secrets-gitlab
revoke token
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 62
- Forks
- 12
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Implement revoke token functionality. Currently, generated tokens are either expired or manually revoked. No-longer-needed token should also be revoked programmatically.
AC:
generic path revoke which accepts below to revoke
{
"id": ,
"token_id": ,
}
we'll want a control that a only generated token can be revoked by the requested entity. plane /revoke endpoint may not be sufficient for it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing generated-token handling and the Plane /revoke endpoint behavior. Define the generic revoke path accepting project id and token_id, with a check that only the requesting entity can revoke its generated token. Done means no-longer-needed generated tokens can be revoked programmatically without relying only on expiration or manual revocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100