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
[WIP] Switch versions of go-jose and go-oidc #123649
[WIP] Switch versions of go-jose and go-oidc #123649
Conversation
/sig auth |
/kind cleanup |
07eb811
to
ba9b49b
Compare
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
ba9b49b
to
78f9bee
Compare
/retest |
/hold There are behavioral changes in go-oidc v3 that don't match what I would expect from KAS (will link the old PR later). |
Not opposed to making the switch but it needs super careful review which we haven't had bandwidth for yet |
@@ -228,7 +228,7 @@ func TestServiceAccountTokenCreate(t *testing.T) { | |||
} | |||
|
|||
checkPayload(t, treq.Status.Token, `"system:serviceaccount:myns:test-svcacct"`, "sub") | |||
checkPayload(t, treq.Status.Token, `["api"]`, "aud") | |||
checkPayload(t, treq.Status.Token, `"api"`, "aud") |
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.
No payload should change on a dep bump.
apologies, meant to put WIP, but forgot. definitely NOT for 1.30 |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/triage accepted |
square/go-jose
has beenarchived by the owner
since Feb 27, 2023 there is an active community fork here now https://github.com/go-jose/go-jose/coreos/go-oidc
switched over togo-jose/go-jose
on Dec 27, 2022 in *: update go-jose package to latest coreos/go-oidc#360We are late to the party :)
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: