[JIRA] (IDP-1935) SAML2 Auth flow fails to decrypt when using overridden responder id.

[Scott Cantor (Jira)]

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

Re: SAML2 Auth flow fails to decrypt when using overridden responder id. ( https://shibboleth.atlassian.net/browse/IDP-1935?atlOrigin=eyJpIjoiOGUzY2U4YjQyYWE2NDZmOGIwNjBjMTM1MTY0MDkzODkiLCJwIjoiaiJ9 )

No way to really do a simple fix as it turns out, too many APIs in the middle of these calls. It would require a total roto-till.

I think the most expedient solution for “most” people will be to wire in a way to override ths list of recipients so that when decrypting you can feed in “all” of the possible recipient IDs you’re using. That’s not elegant, but there really aren’t decryption use cases that ever make much use of all this machinery “in anger” to actually affect the key lookup process, so I don’t think that will typically break anything.

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

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#100209- sha1:597f6a7 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221018/76e79c30/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-292059b9-7f7f-4690-bcdd-66f820f937f0
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221018/76e79c30/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-69b57a55-b9e3-41dc-af8f-763221db0dcc
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221018/76e79c30/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-c168a328-003b-436e-b0b2-9cdd8b1b2185
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221018/76e79c30/attachment-0005.png>