[JIRA] (JOIDC-11) Support for client_credentials grant

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDC-11 ( https://shibboleth.atlassian.net/browse/JOIDC-11?atlOrigin=eyJpIjoiNjM0NzQ4YzY4NWJmNGQyY2IyYmQ5ZmUxZmJjMjM2MzUiLCJwIjoiaiJ9 )

Re: Support for client_credentials grant ( https://shibboleth.atlassian.net/browse/JOIDC-11?atlOrigin=eyJpIjoiNjM0NzQ4YzY4NWJmNGQyY2IyYmQ5ZmUxZmJjMjM2MzUiLCJwIjoiaiJ9 )

Committed a first redesign that implements the concept of a second relying party representing the resource server/audience living under the outbound message context and adjusted flow wiring and some beans to handle the change. Control point for allowing unregistered audiences is working, but unregistered clients are TBD because the original OIDC actions don’t allow for it yet.

For the moment attribute filtering requester ID is wired up as the resource server but still debating that.

Some of the design was adjusted to think ahead to what will happen when a 4 legged flow is involved, so I abandoned the idea of replacing the original client RelyingPartyContext in favor of adding one for the resource server so both are available. Probably need to think through that more fully in deciding how the attribute resolution/filtering contexts are handled so it works for the code grant use case later.

( https://shibboleth.atlassian.net/browse/JOIDC-11#add-comment?atlOrigin=eyJpIjoiNjM0NzQ4YzY4NWJmNGQyY2IyYmQ5ZmUxZmJjMjM2MzUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-11#add-comment?atlOrigin=eyJpIjoiNjM0NzQ4YzY4NWJmNGQyY2IyYmQ5ZmUxZmJjMjM2MzUiLCJwIjoiaiJ9 )

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#100191- sha1:993dea2 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/33ac50d2/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-d424e839-016d-42bf-85f9-132650e76950
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/33ac50d2/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-25c6ad0b-b073-4e9b-bff2-e10cbdd747d2
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/33ac50d2/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-e7dfffcf-f6a5-454e-8e95-732b766c47ce
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/33ac50d2/attachment-0005.png>