[JIRA] (JOIDC-104) Support to manipulate claims within the ID_Token
Henri Mikkonen (Jira)
jira at shibboleth.atlassian.net
Fri May 20 08:07:44 UTC 2022
Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-104 ( https://shibboleth.atlassian.net/browse/JOIDC-104?atlOrigin=eyJpIjoiMDRkODQwOGExYWQ5NDE2ODkwNmNkZmI3ZGNlODMwODUiLCJwIjoiaiJ9 )
Re: Support to manipulate claims within the ID_Token ( https://shibboleth.atlassian.net/browse/JOIDC-104?atlOrigin=eyJpIjoiMDRkODQwOGExYWQ5NDE2ODkwNmNkZmI3ZGNlODMwODUiLCJwIjoiaiJ9 )
Committed an initial proposal how this could be tackled:
* Added profile configuration hook for wiring a function producing a Map<String,Object> to be used for replacing the existing claims for id_token
* New SWF action (ManipulateClaimsForIDToken) exploits the function and if the function produces a non-null Map, it replaces the idToken in OIDCAuthenticationResponseContext with the contents of the Map
* The use of Map<String,Object> felt better than using Nimbus-classes (IDTokenClaimsSet or other) to keep the full control on our API
TODO:
* Improve unit testing: it should make sure that we notice possible changes in Nimbus API (JWTClaimsSet. parse (Map) and IDTokenClaimsSet)
* Documentation
( https://shibboleth.atlassian.net/browse/JOIDC-104#add-comment?atlOrigin=eyJpIjoiMDRkODQwOGExYWQ5NDE2ODkwNmNkZmI3ZGNlODMwODUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-104#add-comment?atlOrigin=eyJpIjoiMDRkODQwOGExYWQ5NDE2ODkwNmNkZmI3ZGNlODMwODUiLCJwIjoiaiJ9 )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- sha1:0f60739 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/a919e964/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-8a46e001-9d92-4efc-b3a4-20e997947ed8
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/a919e964/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c79749eb-6e60-4e67-b940-b0b5aacedfb6
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/a919e964/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-543debf2-e73a-4a43-a46b-38e8ba1096b0
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/a919e964/attachment-0005.png>
More information about the commits
mailing list