Delegation...obtaining the ESR endpoint....

[Brent Putman]

On 5/11/12 12:33 PM, Cantor, Scott wrote:
> On 5/11/12 12:25 PM, "Steven Carmody" <Steven_Carmody at brown.edu> wrote:
>> Any suggestions on how to get an IDP to include this attribute in its
>> response ? (because the value is itself an XML document)
> I believe that's done by the delegation SSO profile handler in the IdP, so
> it's automatic.


Yes, that's correct.  It post-processes the Assertion with additional
markup for delegation-related requirements, including adding an
Attribute with the EPR.


>
>> 2) Looking at the example .... I don't see a pointer to the IdP's SSOS
>> ... the attribute seems to be all static data ? Should a url be included
>> as the value of the wsa:Address element ?
> I wouldn't assume that the example matches what we put in the code, and
> the code looks like it populates Address with the value from the IdP's
> metadata, so it's another case of relying on its own metadata to figure
> out an endpoint to send out in a message. Same kind of thing it does with
> the artifact binding to find the index to include in the artifact.
>
> So you have to add an SSOS element with the Liberty SOAP binding as an
> endpoint in the idp-metadata.xml file it loads.


Yes.  The endpoint URL to add to the IdP's copy of its own metadata is
documented in step #6 of the delegation extensions INSTALL.txt.