8000 Supporting OAuth 2.1 for confidential clients by tnorimat · Pull Request #25318 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Supporting OAuth 2.1 for confidential clients - #25318

Merged
mposolda merged 1 commit into
keycloak:mainfrom
Hitachi:ISSUE-25314-OAuth-2-1-Confidential-Client
Feb 22, 2024
Merged

mposolda merged 1 commit into
keycloak:mainfrom
Hitachi:ISSUE-25314-OAuth-2-1-Confidential-Client

Conversation

@tnorimat
@tnorimat tnorimat commented Dec 6, 2023
Copy link
Copy Markdown
Contributor

closes #25314

@mposolda
Copy link
Copy Markdown
Contributor

@tnorimat Looks good. So looks again that missing parts are tests and docs?

@mposolda mposolda self-assigned this Dec 11, 2023
@tnorimat
Copy link
Copy Markdown
Contributor Author

@mposolda Yes, this PR lacks tests and docs. Therefore, I sent the PR as Draft-PR. I am now working on them.

Moreover, I investigated the OAuth 2.1 specification thoroughly and found that I need do to some work.
For example, adding a new executor for matching redirect_uri by considering IPv4/IPv6 loopback addresses and private-use URI schemes(custom URL schemes) for native-app clients.

@mposolda mposolda left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tnorimat Thanks! Added minor comment regarding documentation.

@mposolda
Copy link
Copy Markdown
Contributor

@andymunro Could you please review documentation part of this PR?

closes keycloak#25314

Co-authored-by: shigeyuki kabano <shigeyuki.kabano.sj@hitachi.com>
Signed-off-by: Takashi Norimatsu <takashi.norimatsu.ws@hitachi.com>
@keycloak-github-bot keycloak-github-bot Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unreported flaky test detected, please review

@keycloak-github-bot
Copy link
Copy Markdown

Unreported flaky test detected

If the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR.

org.keycloak.testsuite.ui.account2.UpdateEmailTest#updateEmailLinkNotVisibleWithoutUpdateEmailActionEnabled

Keycloak CI - Account Console IT (chrome)

org.openqa.selenium.NoSuchElementException: 
no such element: Unable to locate element: {"method":"css selector","selector":"#username"}
  (Session info: chrome-headless-shell=121.0.6167.184)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:19:58.91Z'
...

Report flaky test

@mposolda mposolda left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tnorimat @andymunro Thanks for the review and all the updates to this PR!

@mposolda
mposolda merged commit 9ea679f into keycloak:main Feb 22, 2024
@tnorimat
tnorimat deleted the ISSUE-25314-OAuth-2-1-Confidential-Client branch February 22, 2024 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Supporting OAuth 2.1 for confidential clients

3 participants

0