Resolving attributes from a SAML proxy

[Wessel, Keith]

Can you at least tell me if the attribute context and the relying party context should be in the profile request context when its assigned to the input passed into my authnContextTranslationStrategyEX function? I'll put some if statements in there to test and see if they are, but it'd be nice to know if they're _supposed_ to be.

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Friday, October 8, 2021 1:52 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Resolving attributes from a SAML proxy

On 10/8/21, 2:46 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    That's what I thought. So, why am I getting the warning in the log 
> stating that it can't find the attribute resolution context? Has attribute resolution not taken place yet?

It wants an AttributeContext, it's not resolving anything. I can't tell you why, there's no way I could debug this without actually doing it. Either the RelyingPartyContext is missing or the AttributeContext is missing I assume.

Is there really no way to simply make Azure follow the standard here? I can't fathom how that could be less hassle than trying to do this.

But I can't help you other than to attempt it myself, which wouldn't be until next week sometime.

-- Scott


--
For Consortium Member technical support, see https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!DZ3fjg!qQRX1uMcJYYTVnw3qaIKbTrFZ26GFCgkxvRL0ONS6XVLQJXRaYF9NU15kggJgTaBCA$
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net