[JIRA] (JOIDCRP-10) Improve scope resolution for Authentication Requests

[Scott Cantor (Jira)]

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

Re: Improve scope resolution for Authentication Requests ( https://shibboleth.atlassian.net/browse/JOIDCRP-10?atlOrigin=eyJpIjoiNWMyYzIzZGE0ZGVhNGUyOWE0MjkwNjljZTZhNTBlZjEiLCJwIjoiaiJ9 )

I didn’t actually look at what is currently being done, but the intent here as with SAML is that we use the same pattern and layout we do with all the other flows:

* Identity relying party (the OP) and init RelyingPartyContext.
* Attempt metadata lookup
* Populate RelyingPartyContext appropriately
* SelectRelyingPartyConfiguration
* SelectProfileConfiguration (in this case the OIDCSSO profile used now for outbound)

Once that’s done, you can hang anything missing off the profile config as needed to get at it for configuring the flow.

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

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#100192- sha1:e250074 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/3c732429/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-2d0286b1-6fa7-4590-8766-cb733f85b73a
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/3c732429/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-d28a05eb-4176-413c-94e1-552dea82f41e
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/3c732429/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-9fc21550-1a30-49e6-9efa-0ea19d4468a7
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220217/3c732429/attachment-0005.png>