[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=eyJpIjoiMGQzZjZlN2NjZWE0NGYwYmI5MWJjNWZkZGNkN2QzYzQiLCJwIjoiaiJ9 )

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

Quick read through of the token endpoint suggests a couple of noteworthies:

* The ValidateGrant and ValidateGrantType actions are where all the logic seems to be centralized for processing the code and refresh token grants. They also assume they’re pulling claims out of the sealed string, and those get used (among other ways I guess) for re-injecting those claims into the tokens.
* We obviously need to route around a simple action to support a subflow-based model for implementing the other grant types. Later on we can consider refactoring to turn those grant types into their own login flows so we don’t have to special-case them.
* Need to make sure not having any claims embedded in the grant is not a problem, since there won’t be any in this case or the resource owner password case.
* We’ll need to be able to route around the ID token generation steps, I presume based on the absence of the openid scope in the request, but will explore this.

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

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#100183- sha1:c958b34 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211130/c9c1edf0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-376eef6a-3f46-4b57-be29-097788a26e47
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211130/c9c1edf0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-257aad1b-d452-4730-8866-99c164c5745e
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211130/c9c1edf0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-df78a867-101d-4fc0-bbec-2da36dc111a1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211130/c9c1edf0/attachment-0005.png>