-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Azure DevOps token source and validator #54667
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
Merged
strideynet
merged 19 commits into
master
from
strideynet/azure-devops-source-and-validator
May 13, 2025
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
2a7082c
Initial impl of token source
strideynet 53aa49b
Add initial token validator implementation
strideynet 153af66
add join attrs for azure devops
strideynet 06df84e
Switch to Zitadel OIDC
strideynet 61f07d4
Embed zoidc.TokenClaims into main IDTokenClaims struct
strideynet 2928832
Add notes on caching
strideynet 92378ab
Expand concept of token validator
strideynet f4cae2d
Start hacking on test suite
strideynet 7e49082
JoinAttrs method
strideynet bce72e8
Fix TestIDTokenValidator_Validate suite
strideynet de729a0
Update OIDC doc to match real one
strideynet 226e2a6
Add TestIDTokenSource
strideynet abf8a7e
go mod tidy
strideynet 038813a
rearrange go.mod
strideynet 66bc978
fix query params
strideynet bc7846d
RepositoryReference -> RepositoryRef
strideynet 5c8c74b
Switch to azuredevops
strideynet d3d314f
Adjust struct init
strideynet 75be296
Update lib/azuredevops/token_validator.go
strideynet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
242 changes: 228 additions & 14 deletions
242
api/gen/proto/go/teleport/workloadidentity/v1/join_attrs.pb.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we be thinking about moving all uses of go-jose/v3 to go-jose/v4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used go-jose v4 in the tests here since that is what was being used indirectly by the Zitadel OIDC package.
As for if we ought to migrate more fully - it looks like v4 mostly included breaking changes to make it harder to footgun common JWT vulnerabilities (https://github.com/go-jose/go-jose/releases/tag/v4.0.0) - most of these should be pretty easy to adopt. I don't think there's any rush though since they seem to be still releasing new patches for v3.