[JIRA] (JOIDC-128) Support OAuth authorization requests

[Henri Mikkonen (Jira)]

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

Re: Support OAuth authorization requests ( https://shibboleth.atlassian.net/browse/JOIDC-128?atlOrigin=eyJpIjoiZDU3Njc5MDZlZmM4NDJiMWI5OGI0NWUzYjExYmMzYWIiLCJwIjoiaiJ9 )

The authorize -flow now contains a decision-state before decoding:

* If the requested scope contains ‘openid’, the request is considered as OIDC authentication request.
* OAuth authorization request otherwise.

3.1.2.1 of core spec declares that OpenID Connect requests MUST contain the openid scope value. It’s also requirement when request object or request object reference is used.

Moved the following actions into net.shibboleth.idp.plugin.oidc.op.oauth2.profile.impl : DecryptRequestObject, SetAuthorizationCodeToResponseContext, SetRequestObjectToResponseContext, ValidateCodeChallenge, ValidateRedirectURI, ValidateRequestObject, ValidateResponseType, ValidateScope.

Also updated various lookup functions to be compatible with OAuth authorization request messages if they were not solely related to OIDC authentication requests.

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

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#100207- sha1:bddf6e1 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221003/09cead79/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-cf32e647-118f-47c7-80d5-03f33777fe28
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221003/09cead79/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-050dadff-1d4f-4187-9ee7-5509a83d0150
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221003/09cead79/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-d1a0b29d-97f8-4601-aa5c-64bc05151d5a
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221003/09cead79/attachment-0005.png>