[JIRA] (JOIDC-78) Wrong JSONObject type when decoding claims from Signed JAR Authentication request

Simone Avogadro (Jira) jira at shibboleth.atlassian.net
Wed Mar 9 22:09:42 UTC 2022


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

Re: Wrong JSONObject type when decoding claims from Signed JAR Authentication request ( https://shibboleth.atlassian.net/browse/JOIDC-78?atlOrigin=eyJpIjoiM2NmNTRjZjg2MzE4NGM4ZTk5ZDljZDFkNjc5Y2RlMmUiLCJwIjoiaiJ9 )

Sorry for not being clear: JAR=JWT Authenticated Request
I’ve configured
idp.oidc.tokenEndpointAuthMethods = private_key_jwt

inside oidc.properties and thus the initial authentication request happens by embedding all the request parameters with a JWT wihch is then signed and passed as a single URL.

All the other parameters are being read correctly (acr_values, client_id, scope etc….) but the “claims” one does not seem to work.

I’m double checking if I added any property/class to the webapp which might cause this but so far it doesn’t seem so: I’ll report updates on this in case I find any workaround/urther information

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

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#100196- sha1:dfd693a )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220309/b339837b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-c4f864bb-e802-4125-a6e4-dd4de99035fd
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220309/b339837b/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-be840843-e215-41d3-97ea-ddf1ee41b7d6
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220309/b339837b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-3651d186-9e50-48a7-b209-cd692a1e44af
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220309/b339837b/attachment-0005.png>


More information about the commits mailing list