[JIRA] (JOIDC-104) Support to manipulate claims within the ID_Token

Simone Avogadro (Jira) jira at shibboleth.atlassian.net
Fri May 20 07:51:54 UTC 2022


Simone Avogadro ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A60a84ee1-4961-471b-99d8-f67c05e24403 ) *commented* on JOIDC-104 ( https://shibboleth.atlassian.net/browse/JOIDC-104?atlOrigin=eyJpIjoiZmQ5NjMzMmFiNWYyNDEyYjkyZjVjMzk3Nzc0NmU3MTEiLCJwIjoiaiJ9 )

Re: Support to manipulate claims within the ID_Token ( https://shibboleth.atlassian.net/browse/JOIDC-104?atlOrigin=eyJpIjoiZmQ5NjMzMmFiNWYyNDEyYjkyZjVjMzk3Nzc0NmU3MTEiLCJwIjoiaiJ9 )

I see that you’ve related this to https://shibboleth.atlassian.net/browse/JOIDC-97 so a couple of considerations:

* in order to generate the correct c_hash the code will need to know the code  }} and the  {{ alg Header Parameter of the ID Token's JOSE Header. I tried doing it within the attribute resolverr but failed because I lacked these information
* if the solution will be to allow ID_Token manipulation (the most general solution!) in order to address the c_hash then that code will need to have access to that same infomration (code and alg for ID_Token JOSE), even when using refresh_tokens => this probably makes impratical to use https://shibboleth.atlassian.net/browse/JOIDC-104 in order to generate the c_hash per https://shibboleth.atlassian.net/browse/JOIDC-97 because ti would probably complicate this task too much

( https://shibboleth.atlassian.net/browse/JOIDC-104#add-comment?atlOrigin=eyJpIjoiZmQ5NjMzMmFiNWYyNDEyYjkyZjVjMzk3Nzc0NmU3MTEiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-104#add-comment?atlOrigin=eyJpIjoiZmQ5NjMzMmFiNWYyNDEyYjkyZjVjMzk3Nzc0NmU3MTEiLCJwIjoiaiJ9 )

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/bc132996/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-4332b9e3-38c6-4f25-8997-ea04341aaebb
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/bc132996/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-389cbb60-3a08-4347-9df7-e7f466707dc9
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/bc132996/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a820f8de-52bc-48f2-b9f8-22322adf9c04
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220520/bc132996/attachment-0005.png>


More information about the commits mailing list