[JIRA] (JOIDC-97) support C_HASH in ID_Token also for Authorization Code Flow with PKCE

Henri Mikkonen (Jira) jira at shibboleth.atlassian.net
Tue May 17 12:03:01 UTC 2022


Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-97 ( https://shibboleth.atlassian.net/browse/JOIDC-97?atlOrigin=eyJpIjoiMWQ4MDcxYTAzZDM0NDczMWI2MDczZjM4NWYzYmYwY2EiLCJwIjoiaiJ9 )

Re: support C_HASH in ID_Token also for Authorization Code Flow with PKCE ( https://shibboleth.atlassian.net/browse/JOIDC-97?atlOrigin=eyJpIjoiMWQ4MDcxYTAzZDM0NDczMWI2MDczZjM4NWYzYmYwY2EiLCJwIjoiaiJ9 )

In the OIDC core spec, the _c_hash_ claim is only mentioned under the section *3.3. Authentication using the Hybrid Flow*. Over there, it’s specified that it’s required when id_token is issued from the authorization endpoint together with the authorization code. So, it clearly refers to hybrid flow only. In the sections for the authorization code flow and implicit flow (3.1 and 3.2), the claim _c_hash_ is not mentioned at all.

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

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:70dbdd1 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220517/c1c5f3a6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-dd68e9c5-ad9e-4bdd-ab73-8a22765dc13a
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220517/c1c5f3a6/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c320f6f7-0205-4445-9028-22dc00aa968a
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220517/c1c5f3a6/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-5a5f419e-8ab4-42db-b704-a1c93d43a746
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220517/c1c5f3a6/attachment-0005.png>


More information about the commits mailing list