[JIRA] (JSATTR-2) Move PRC lookup strategy into resolution context

Rod Widdowson (Jira) jira at shibboleth.atlassian.net
Tue Aug 16 14:15:43 UTC 2022


Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on JSATTR-2 ( https://shibboleth.atlassian.net/browse/JSATTR-2?atlOrigin=eyJpIjoiMDUwNjY0YzlhMzhjNDRkZGJkNjhjZjM1ODUxMzZlM2UiLCJwIjoiaiJ9 )

Re: Move PRC lookup strategy into resolution context ( https://shibboleth.atlassian.net/browse/JSATTR-2?atlOrigin=eyJpIjoiMDUwNjY0YzlhMzhjNDRkZGJkNjhjZjM1ODUxMzZlM2UiLCJwIjoiaiJ9 )

After discussion with Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) I’ll

* fix the remaining strategy in V5
* review usage in V4 adding deprecations, double checking that the same removals are in V5.

Then we can call this done.
Its worth noting that there is no configuration to replace this. Everywhere that ARC is created, we already have a PRC (and are adding the latter into the former) so we can add an appropriate strategy. If this stops being true in the future then we can add the configuration at that point.

…..and if there *is* a case where it is currently being used then we will find out when 4.3 goes out

( https://shibboleth.atlassian.net/browse/JSATTR-2#add-comment?atlOrigin=eyJpIjoiMDUwNjY0YzlhMzhjNDRkZGJkNjhjZjM1ODUxMzZlM2UiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JSATTR-2#add-comment?atlOrigin=eyJpIjoiMDUwNjY0YzlhMzhjNDRkZGJkNjhjZjM1ODUxMzZlM2UiLCJwIjoiaiJ9 )

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#100204- sha1:f005d5a )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220816/bd36905e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-5b2a846f-c3c9-4554-bb9d-b1f803f53b71
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220816/bd36905e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-9087c817-2c93-4ff9-b740-5a756d90ee6d
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220816/bd36905e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-9766dca9-2767-4921-91ab-8cf5616b1965
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220816/bd36905e/attachment-0005.png>


More information about the commits mailing list