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

Tue Nov 15 13:56:14 UTC 2022

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=eyJpIjoiMmYzZmM1OGY4YzY1NGYyNzliN2I2OWFkNDc5YTY2NjAiLCJwIjoiaiJ9 )

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

During documentation I realized that we should actually have a flag for keep up requiring the use of OIDC authentication flow by the RPs. It should probably default to true to keep the OP plugin working as before by default.

The flag should perhaps be implemented as a profile configuration predicate, but that would require some changes to the oidc-common module. Maybe we could already support a Predicate<PRC> (configurable via property) that’s wired to some authorization-flow action now “directly”, and after next oidc-common minor upgrade via profile configuration property

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

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#100210- sha1:28a3636 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221115/af407906/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-cf7936fe-f31d-431c-894e-41d85b4fd3c9
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221115/af407906/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-e23ce84c-d46a-4a35-be69-0a923113af91
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221115/af407906/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-help_16-a570ec20-108d-41cd-b5ec-48baaa7cdf81
Type: image/png
Size: 613 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221115/af407906/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-87f07043-7f30-4b62-8251-ea4bc70c77e4
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221115/af407906/attachment-0007.png>