-
Notifications
You must be signed in to change notification settings - Fork 374
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
Fix access token attributes for federated user #2653
Fix access token attributes for federated user #2653
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2653 +/- ##
=========================================
Coverage ? 56.31%
Complexity ? 8233
=========================================
Files ? 632
Lines ? 46672
Branches ? 8592
=========================================
Hits ? 26282
Misses ? 16637
Partials ? 3753
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
LGTM, please address the comments and let's run the integration tests
} | ||
|
||
SessionDataCacheEntry sessionDataCacheEntry = oAuthMessage.getSessionDataCacheEntry(); | ||
if (sessionDataCacheEntry == null || mappedRemoteClaims.get().isEmpty()) { |
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.
This logic can go with line 434
mappedRemoteClaims.get().isEmpty()) {
log.debug("Retrieving claims cached against authorization_code for user: " + | ||
requestMsgCtx.getAuthorizedUser()); | ||
} | ||
if (isEmpty(userAttributes)) { |
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.
repetitive checks
PR builder started |
PR builder completed |
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.
let's run the pr builder before merging
PR builder started |
PR builder completed |
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.
Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/12393258772
Proposed changes in this pull request
In this PR, we are getting locally mapped remote claims from framework to resolve access token attributes in federated login. From framework we are adding mapped remote claims to authn results and we are using this from oauth side to resolve federated user attributes.
When should this PR be merged
[Please describe any preconditions that need to be addressed before we
can merge this pull request.]
Follow up actions
[List any possible follow-up actions here; for instance, testing data
migrations, software that we need to install on staging and production
environments.]
Checklist (for reviewing)
General
Functionality
Code
Tests
Security
Documentation