Getting the requesting SP's entityID during multi-factor script execution

[Wessel, Keith]

Thank you, gentlemen. That did the trick.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Jim Fox
Sent: Thursday, June 01, 2017 10:49 AM
To: Shib Users <users at shibboleth.net>
Subject: RE: Getting the requesting SP's entityID during multi-factor script execution


>> The problem is that when the attribute script runs to populate values for the
>> MFA script, the requesting SP seems to be unavailable. I tested this by
>> logging the value of resolutionContext.getAttributeRecipientID(), and it's
>> null. Of course, when the script runs later doing the normal attribute
>> resolution work, the entityID of the SP is available.
>
> If you want it populated, you just have to set it. Just call setAttributeRecipientID before you invoke the resolver.
>
> The relying party name is in the RelyingPartyContext "child" via getRelyingPartyId()
>

In an MFA script you can use this

  rpid = input.getSubcontext("net.shibboleth.idp.profile.context.RelyingPartyContext").relyingPartyId;

Jim
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net