[JIRA] (JOIDCRP-17) Add JWT Encryption Parameter Resolver Support

[Philip Smart (Jira)]

Philip Smart ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=5afecdc1eb3ffa0c596652c4 ) *commented* on JOIDCRP-17 ( https://shibboleth.atlassian.net/browse/JOIDCRP-17?atlOrigin=eyJpIjoiN2JjOTE1YWU4ZTQ2NDIyNmJkNjUxNWU5M2MzY2E3MDkiLCJwIjoiaiJ9 )

Re: Add JWT Encryption Parameter Resolver Support ( https://shibboleth.atlassian.net/browse/JOIDCRP-17?atlOrigin=eyJpIjoiN2JjOTE1YWU4ZTQ2NDIyNmJkNjUxNWU5M2MzY2E3MDkiLCJwIjoiaiJ9 )

I’ve added an OpenID Provider metadata encryption parameter resolver to the RP. It currently does not support Direction Encryption ‘dir’ modes. I do not believe the OP does either, I think there are a few things that would need to be added e.g. an AlgorithmDescriptor which is supported by the runtime - unless those checks can be ignored for that as a special case. That said, I would say direct encryption is a low priority, it seems unlikely an OP would only support ‘Dir’ and not ‘Key Encryption via RSA’ - although there are no ‘required’ key management modes in the JWA spec.

Key agreement using ECDH-ES is proving tricky to test, as the runtime (or at least my runtime) does not support the JCA algorithm ID of EC/ECB/PKCS1Padding , which is how the JWA KeyAgreementECDHES class presents itself. And that is the only one registered in commons crypto API. I am not really sure what the JCA algorithm ID should actually be for this. I do not think the OP supports this by default (and I might see why).

( https://shibboleth.atlassian.net/browse/JOIDCRP-17#add-comment?atlOrigin=eyJpIjoiN2JjOTE1YWU4ZTQ2NDIyNmJkNjUxNWU5M2MzY2E3MDkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDCRP-17#add-comment?atlOrigin=eyJpIjoiN2JjOTE1YWU4ZTQ2NDIyNmJkNjUxNWU5M2MzY2E3MDkiLCJwIjoiaiJ9 )

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#100202- sha1:0ba1f75 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220722/33bfea66/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-95095bf7-b1f9-455a-a40f-87c46021b763
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220722/33bfea66/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3de00a52-81c4-413d-a75a-e45d0256ff8a
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220722/33bfea66/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-3df7971b-9c96-4c53-8cb5-e2453275b7cb
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220722/33bfea66/attachment-0005.png>