[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=eyJpIjoiYzliMjk4ZDA0YTQzNDZmYjk3Y2NkYTQ5NjZiNDk3YjQiLCJwIjoiaiJ9 )

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

I moved the ProviderMetadataEncryptionParametersResolver into commons alongside the new BasicJWTEncryptionParametersResolver. If Brent Putman ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A97de0981-adc3-4044-95ed-131622fad81e ) has time to check over those, that would be great.

I guess one of the significant differences over the SAML param resolvers is; It loops over the algorithms in the config, and finds a credential that is compatible (either locally or from the providers keyset in metadata). Whereas, in the SAML case, I think it loops over the credentials and checks for a compatible algorithm. I could obviously change it to work the same way, I am not sure how much it matters.

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

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#100205- sha1:5460ff5 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220819/eff5f10a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-a69bfa61-b950-4359-a64b-1690d63626e5
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220819/eff5f10a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-131226d9-850c-4824-90d5-89fe679866bc
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220819/eff5f10a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-05490d4c-1085-4665-a2b1-d3e90e8ea360
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220819/eff5f10a/attachment-0005.png>