[JIRA] (IDP-1867) No attribute context available in profile request context for authenContextTranslationStrategyEx hook

[Scott Cantor (Jira)]

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

Re: No attribute context available in profile request context for authenContextTranslationStrategyEx hook ( https://shibboleth.atlassian.net/browse/IDP-1867?atlOrigin=eyJpIjoiY2FlMmU5MjgxYWJlNDExMTkwMTI0MmNlZWI4Mzk1OGEiLCJwIjoiaiJ9 )

It is in fact a bug in the code that’s locating the PRC to pass into your function. This is all confusing on a whole other level because of how the proxy logic was implemented without completely rewriting all our code, and we actually nest a whole new PRC tree underneath a node in the original tree. It’s like a sub-transaction operating within the original transaction because it’s a second message exchange inside the first one. It all works, but is very complex to keep straight in the code.

I messed up by tracking back to the wrong ProfileRequestContext instead of the nested one that actually sits on top of where the AttributeContext lives.

It’s possible to work around, but once I fix the code, it will break your workaround, though I guess it could done with a script that acts defensively and could detect the change and handle both cases. Probably easier just to make a note and drop the workaround once the patch is out.

I’m ok fixing this as is since this is a very little used feature but it’s unfortunate, and I’m going to simply blame Azure and their garbage pile of bugs for all of this.

I will have to test a workaround for it first and then once I have that I can patch the code and test it without.

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

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#100181- sha1:c5b808b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211012/fdaf726c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3c80ac5b-ecbf-4a2a-8c13-c7a2738c473c
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211012/fdaf726c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-3168a362-3f60-4534-aff0-8ab5e8514409
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211012/fdaf726c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-8926fff4-e256-44ef-a167-f12dd3bc7cbc
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211012/fdaf726c/attachment-0005.png>