[JIRA] (JCOMOIDC-45) Add a Decrypter for JWE tokens similar to the opensaml Decrypter

[Philip Smart (Jira)]

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

Re: Add a Decrypter for JWE tokens similar to the opensaml Decrypter ( https://shibboleth.atlassian.net/browse/JCOMOIDC-45?atlOrigin=eyJpIjoiNjExZGNmMzQ1MDVhNGRhNDkyYTA4YzZjMDM5ZmUzZjEiLCJwIjoiaiJ9 )

All key management modes have the following criterion:

* KeyUsage
* KeyID (if present)
* JOSEObject included - not used atm.

I’ve added the following criterion specific to the following key management modes:

* *Direct Encryption*. As the RP can resolve the actual encryption key, we can filter on: * Encryption KeyAlgorithm e.g. AES.
* KeyLength

* *Key Encryption*. We do not validate the un-encrypted key, the Nimbus decrypted does. * KeyAlgorithm from key management mode ('alg') algorithm e.g. RSA for RSA-OAEP

* *Key Wrapping*. We do not validate the un-warpped key, the Nimbus decrypted does. * KeyAlgorithm from key management mode ('alg') algorithm e.g. AES for A128KW
* KeyLength - extracted from the algorithm e.g. 128 bit for A128KW

* *Key Agreement* * Not yet working.

Credentials from the various resolvers are filtered against these by the AbstractCriteriaFilteringCredentialResolver.

The JWT decrypted class still contains further and slightly overlapping JOSE Header v credential (albeit a filtered down set) validation.

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

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:365db85 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220715/6af4331a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-04793a80-4754-4f49-b03d-cf448ac581d0
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220715/6af4331a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-e9d9c196-666b-4b50-bcdc-a778bffc0745
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220715/6af4331a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-6b6c946f-bd68-40c7-8d2c-0f48b4b1293f
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220715/6af4331a/attachment-0005.png>