[JIRA] (JCOMOIDC-41) Move OIDC Signature Validation resolvers and parameter classes to commons

[Brent Putman (Jira)]

Brent Putman ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A97de0981-adc3-4044-95ed-131622fad81e ) *commented* on JCOMOIDC-41 ( https://shibboleth.atlassian.net/browse/JCOMOIDC-41?atlOrigin=eyJpIjoiZDAzMDRlN2QyOGYwNDkxM2IxYjNjZThiNTZkOGE0NjUiLCJwIjoiaiJ9 )

Re: Move OIDC Signature Validation resolvers and parameter classes to commons ( https://shibboleth.atlassian.net/browse/JCOMOIDC-41?atlOrigin=eyJpIjoiZDAzMDRlN2QyOGYwNDkxM2IxYjNjZThiNTZkOGE0NjUiLCJwIjoiaiJ9 )

I pushed some draft code up to a dev branch.

Pending is:

* Final/permanent way to turn a Nimbus JWK into a Credential. For now, just copied code from the KeyInfo resolver plugin. Maybe is good enough, given that Nimbus has already done most of the work that the KeyInfoCredentialResolver does for the XML case.
* Signature algorithm include/exclude processing. Not sure how the -Configuration, -Parameters, and -Criterion classes will work here wrt to the IdP config and context.

* Also at question is whether we use algo URIs or the native JOSE identifiers in the config and params.
* Related: OIDCSignatureValidationParameters seems to be extending the wrong class (currently the Signing one, not the Valudation one). The one its extending doesn’t have the include/exclude algos.

* As Scott said, the main thing - which is key to how all this works - is having the right CredentialResolver for the trusted Credentials. At least for the SAML metadata case (MetadataCredentialResolver), that component is substantially more complicated than the trust engine itself.

( https://shibboleth.atlassian.net/browse/JCOMOIDC-41#add-comment?atlOrigin=eyJpIjoiZDAzMDRlN2QyOGYwNDkxM2IxYjNjZThiNTZkOGE0NjUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JCOMOIDC-41#add-comment?atlOrigin=eyJpIjoiZDAzMDRlN2QyOGYwNDkxM2IxYjNjZThiNTZkOGE0NjUiLCJwIjoiaiJ9 )

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#100192- sha1:e250074 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220218/6d74b38d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-18febb17-5a95-4868-9b47-e28af4d72dc5
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220218/6d74b38d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-811643ea-920a-4e4e-910a-19f656cf7ac9
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220218/6d74b38d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-62b9f74e-4718-492b-9a82-19bf84fc5acd
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220218/6d74b38d/attachment-0005.png>