[JIRA] (IDP-1902) Support alternative RelyingPartyContext lookup in RP config resolver

[Scott Cantor (Jira)]

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

Re: Support alternative RelyingPartyContext lookup in RP config resolver ( https://shibboleth.atlassian.net/browse/IDP-1902?atlOrigin=eyJpIjoiM2Y5OTUzOWViZDhlNGY4ZWI5ZmI4MGJiODhlMDc0ZjYiLCJwIjoiaiJ9 )

After reviewing the delegating resolver Brent built, that’s the simpler fix for this problem for now. I changed the original SelectRPConfiguration action so that it can use either the standard resolver or the criteria-based version and checks for the case where the RP context isn’t in the expected place. Wraps it in a new temporary PRC for the call if necessary. This won’t change any existing flows that use the old action, but the new use case can inject the alternate resolver we already have defined in the services layer and do the right thing.

( https://shibboleth.atlassian.net/browse/IDP-1902#add-comment?atlOrigin=eyJpIjoiM2Y5OTUzOWViZDhlNGY4ZWI5ZmI4MGJiODhlMDc0ZjYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1902#add-comment?atlOrigin=eyJpIjoiM2Y5OTUzOWViZDhlNGY4ZWI5ZmI4MGJiODhlMDc0ZjYiLCJwIjoiaiJ9 )

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/244e1e83/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-443d4b6f-6099-48b5-98a5-5145fc65c21e
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/244e1e83/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-9f302bef-5ca6-42bf-bbb1-e56f3caa2cf3
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/244e1e83/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-828227ee-0db2-455f-9257-62f0b5580e51
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220209/244e1e83/attachment-0005.png>