[JIRA] (JCOMOIDC-48) Move OIDC.SSO profile bean to commons

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JCOMOIDC-48 ( https://shibboleth.atlassian.net/browse/JCOMOIDC-48?atlOrigin=eyJpIjoiOWFhYzA2OGU3ZjY2NDcyZGFjNzRkYTZjMDM1MGQ0ZDIiLCJwIjoiaiJ9 )

Re: Move OIDC.SSO profile bean to commons ( https://shibboleth.atlassian.net/browse/JCOMOIDC-48?atlOrigin=eyJpIjoiOWFhYzA2OGU3ZjY2NDcyZGFjNzRkYTZjMDM1MGQ0ZDIiLCJwIjoiaiJ9 )

I realised today that even though the codebase of the upcoming commons (and RP and OP) is compatible with IdP 4.2.0, the requirement for multiple relying-party/postconfig.xml files will make them requiring IdP 4.3.0 (see https://shibboleth.atlassian.net/browse/JSE-51 ( https://shibboleth.atlassian.net/browse/JSE-51 ) ).

> 
> 
> 
> Sometimes this affects the OP e.g. idp.oidc.rodecrypt.config →
> idp.oidc.decrypt.config
> 
> 

Yeah, those rodecrypt -styled properties were logical with the previous OIDCSecurityConfiguration structure, when we had specific methods for request object decryption + signature validation and token endpoint signature validation parameters. I have to see what’s the best way to keep supporting them for a while in OP.

> 
> 
> 
> Of interest, both the RP and OP expose a keyset flow at different
> locations profile/oidc/rp/keyset and profile/oidc/keyset. I am not sure
> there is much point in having them separate if they, by default, share the
> same key
> 
> 

Also, is a single keyset flow satisfactory for RP, or can we (fore)see a use case when each RP/client registration towards OP would prefer using its own keyset? And in a way that the keysets wouldn’t be published together.

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

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#100214- sha1:c40e72a )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230127/b396f57a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-611c348e-93f3-4cfc-b18e-1bf346a2bdd2
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230127/b396f57a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c981ab59-a11c-4b7e-9a83-7fce338cd2d9
Type: image/png
Size: 448 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230127/b396f57a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-2bc0b968-eef7-409f-99fd-61c9c82bb7e8
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230127/b396f57a/attachment-0005.png>