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

Implement id_tokens support for vault access #1082

Open
Hybris95 opened this issue Jan 30, 2024 · 0 comments
Open

Implement id_tokens support for vault access #1082

Hybris95 opened this issue Jan 30, 2024 · 0 comments
Labels
feature Feature missing according to gitlab ci standard

Comments

@Hybris95
Copy link

Considered current GitLab implementation, they preconise the use of id_tokens (instead of JWT tokens) in order to authenticate to Vault.
Currently, gitlab-ci-local does not take this implementation into account.

Please check following documentation :
https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/

Actually, using the "id_tokens" beacon does not generate any wrapped token.

The old implementation (which is now obsolete) is also not implemented (I'm speaking of CI_JOB_JWT & CI_JOB_JWT_V1 & CI_JOB_JWT_V2) :
https://docs.gitlab.com/ee/update/deprecations.html#old-versions-of-json-web-tokens-are-deprecated

@firecow firecow added the feature Feature missing according to gitlab ci standard label Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature missing according to gitlab ci standard
Projects
None yet
Development

No branches or pull requests

2 participants