[JIRA] (JOIDCRP-13) Client Authentication Resolver

[Philip Smart (Jira)]

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

Re: Client Authentication Resolver ( https://shibboleth.atlassian.net/browse/JOIDCRP-13?atlOrigin=eyJpIjoiOTdjMzBmNmQ3ODVhNDc3NGI5OTQyYTQ4ZTI0N2RmN2QiLCJwIjoiaiJ9 )

As Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) pointed out, having another resolver service for this was unnecessary, instead, adding the logic via a strategy to the profile configuration (which is already a reloadable service). This is now done using the following logic:

* By default, the client authentication lookup strategy constructs a client authentication method from values provided in the oidc properties file (or any properties file if, for example, the secret is in the secrets properties). This allows quick configuration if there is only a single client.
* If there is more than one client e.g. some kind of discovery flow is used to choose the OP, the static property values can be commented out, and the strategy will use a further embedded strategy to lookup the client authentication from the supplied client_id appropriate for that OP.

* The default strategy for this is backed by a storage service. Currently, an in-memory service is constructed from the same map as shown in https://shibboleth.atlassian.net/browse/JOIDCRP-13?focusedCommentId=32417. This would need to be added to the relying party XML by the deployer.

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

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#100197- sha1:838a6ed )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220324/1766400e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-cb03c5a5-3f60-45eb-b949-6100737ba582
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220324/1766400e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-6af6c9cc-7bbe-4b0f-a983-38a15e94ebbc
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220324/1766400e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-4894d0c8-5749-4031-a26c-a0979e684504
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220324/1766400e/attachment-0005.png>