SessionInitiator equivalent of SSO

Matt MacAdam mattjm at uw.edu
Tue Dec 9 13:45:17 EST 2014


Ahh...I thought the SSO element had extremely limited customization,
but I had completely missed this in the attributes section of the SSO
element:

"Other attributes supported include settings specific to various types
of <SessionInitiator> plugins to alter the behavior of specific
protocols...."

It indeed works fine if I just add the outgoingBindings attribute to
the SSO element.  *mind blown*

What would be the appropriate place in the wiki to document something
like this?  Maybe:

https://wiki.shibboleth.net/confluence/display/SHIB2/Contributions#Contributions-Documentation

Thanks so much!

-----
Matt MacAdam
Identity & Access Management Specialist
UW Information Technology
206-616-9842


On Sat, Dec 6, 2014 at 1:01 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 12/5/14, 11:32 PM, "Matt MacAdam" <mattjm at uw.edu> wrote:
>
>>At least that's what I observed while helping out one of our users
>>here--I could be misinterpreting something.  *If* I'm correct...I
>>assume the <SSO> element registers whatever is listed in
>>protocols.xml?
>
> Yes.
>
>>For the curious...this all started because Word handles links in
>>documents partly through an internal browser and often breaks SSO.
>>One of our users wanted to fix this, and was using a workaround
>>published at:
>>
>>https://admin.kuleuven.be/icts/services/aai/documentation/sp/linksfromoffi
>>cetosp.html
>>
>>It works, but you have to either keep the <SSO> element, or create the
>>ACS endpoints manually (blech).
>
> Neither. Just set the property in the SSO element.
>
> This is why it's a mistake to create documentation like that. It loses
> relevance and misleads people any time things change. If people want to
> document something, they should do it in the wiki, because then it will be
> maintained.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list