v3.4.3 HTTPClient attribute resolver

Cantor, Scott cantor.2 at osu.edu
Tue Feb 5 21:00:06 EST 2019


On 2/5/19, 8:57 PM, "users on behalf of Pablo Vidaurri" <users-bounces at shibboleth.net on behalf of psvidaurri at gmail.com> wrote:

> It seems all I had to do was use the correct method:
> $paramEscaper.escape($resolutionContext.principal)

That and you're confusing requestContext (which is a deprecated object that is not part of this connector) with resolutionContext. At least one of the examples is wrong and refers to the wrong variable name. The documentation is and was right. That is the case 90% of the time, examples are never fully tested or accurate.

-- Scott



 




On Tue, Feb 5, 2019 at 7:42 PM Pablo Vidaurri <psvidaurri at gmail.com> wrote:


I've viewed the documentation (as always before I post) but we all know it is not always accurate or updated timely ...


https://wiki.shibboleth.net/confluence/display/IDP30/HTTPConnector has example of 

$pathEscaper.escape($requestContext.principal <https://webservice.example.org/api/subject/$pathEscaper.escape($requestContext.principal)/groups>)
didn't work 


https://wiki.shibboleth.net/confluence/display/IDP30/URLTemplate list a tabled of Template Context which for resolutionContext
 has a description of

"Commonly useful members include $resolutionContext.principal and $resolutionContext.attributeRecipientID "
 ... tried both and doesn't work either.



-psv






On Tue, Feb 5, 2019 at 6:37 PM Cantor, Scott <cantor.2 at osu.edu> wrote:


On 2/5/19, 7:23 PM, "users on behalf of Pablo Vidaurri" <users-bounces at shibboleth.net on behalf of
psvidaurri at gmail.com> wrote:

> All of them are null. What is available during this webservice call? Why is $requestContext.principalName  available in
> my db connector but not in my http connector?

What's available is exactly what's documented. Since $requestContext.principalName is a V2-era deprecated syntax, and is not documented as being supported, it is not available.

> 2) Is there a way to only execute the HttpClient connector in the attribute resolver for only certain sp (entityId)?

Activation conditions are available on virtually every component to address that.

-- Scott



-- 
For Consortium Member technical support, see 
https://wiki.shibboleth.net/confluence/x/coFAAg <https://wiki.shibboleth.net/confluence/x/coFAAg>
To unsubscribe from this list send an email to 
users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>









More information about the users mailing list