[JIRA] (IDP-2054) Add per-SP salt for computedId connector

[Scott Cantor (Jira)]

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

Re: Add per-SP salt for computedId connector ( https://shibboleth.atlassian.net/browse/IDP-2054?atlOrigin=eyJpIjoiOWQ1OTU0ZTZkNTllNDAyMTk2ZmQ0MjU4YTNhODc2NTIiLCJwIjoiaiJ9 )

I’m going to do this in two stages because there’s an API change that will be required to make it fully viable. The interim V4 step will be a BiFunction<ProfileRequestContext,PairwiseId> hook in the computed ID store implementation that sits in between a global salt and the exception map, and will override the global salt if it returns a value (it’s also allowable now to omit the global salt). The limitation is that the ProfileRequestContext input will be null until V5. There are some ways to get hold of the PRC via Spring by way of the servlet request, so it’s roundabout but possible in the interim to get to it.

The PRC will allow for access down into things like resolved attributes and so on, allowing that to be a means of driving the salt lookup without limiting it to that mechanism.

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

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#100212- sha1:99773b8 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221213/cece0e1e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-f2cb5947-2041-4f0a-b984-f708eea6115e
Type: image/png
Size: 302 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221213/cece0e1e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3d93cc04-50a9-43f1-9d53-c7945456ce00
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221213/cece0e1e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-5ec50531-15b8-4d79-a6b6-6066db1b0ef0
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221213/cece0e1e/attachment-0005.png>