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
MGMT-16766: Use client_id
instead of clientId
#6076
MGMT-16766: Use client_id
instead of clientId
#6076
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhernand The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The `clientId` claim will be replaced by `client_id` from the SSO server in order to be compliant with the OAuth2 specification. During a transition period the old `clientId` will be preserved. This patch changes our code so that it first tries to use the newer and more correct `client_id`, and then if it doesn't exist it tries the older `clientId`. In the future we should check if we are really using the value of this `client_id` claim at all. If we aren't then it would probably be good to remove the code completely. Related: https://issues.redhat.com/browse/MGMT-16766 Related: https://datatracker.ietf.org/doc/html/rfc9068#section-2.2 Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
42953c8
to
0403b7e
Compare
/lgtm |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6076 +/- ##
==========================================
+ Coverage 68.40% 68.44% +0.03%
==========================================
Files 239 239
Lines 35457 35575 +118
==========================================
+ Hits 24256 24349 +93
- Misses 9098 9123 +25
Partials 2103 2103
|
@jhernand please retitle the PR with MGMT-16766 |
client_id
instead of clientId
client_id
instead of clientId
@jhernand: This pull request references MGMT-16766 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Done. |
@jhernand: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-agent-installer-api-server-container-v4.16.0-202403122214.p0.g6f671e7.assembly.stream.el8 for distgit ose-agent-installer-api-server. |
The
clientId
claim will be replaced byclient_id
from the SSO server in order to be compliant with the OAuth2 specification. During a transition period the oldclientId
will be preserved. This patch changes our code so that it first tries to use the newer and more correctclient_id
, and then if it doesn't exist it tries the olderclientId
.In the future we should check if we are really using the value of this
client_id
claim at all. If we aren't then it would probably be good to remove the code completely.Related: https://issues.redhat.com/browse/MGMT-16766
Related: https://datatracker.ietf.org/doc/html/rfc9068#section-2.2
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist