Specifying prefixed namespace for SLO requests?

[Curtis Lacy]

Fair enough.  Thanks!


Curtis


> On Apr 10, 2017, at 11:22 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
>> Doesn’t this effectively make it impossible to accept encrypted logout
>> requests?  Or is it more common for SPs to include the namespace
>> definitions in the encrypted snippets themselves?
> 
> SAML logout in general is relatively uncommon and I doubt encryption is used very often with it. I have little to no experience with how it works in practice.
> 
> My guess is so few implementations support it outside of the major products that it just doesn't come up much. Shibboleth IdPs didn't support inbound encryption until 3.0 and there's no use of it in any of the federations in academia, for example.
> 
> As a matter of practicality, it's understood (by us) that using XML Encryption really requires that the encrypted XML be well-formed (or is when I bother to refresh my memory about it). How much that's understood by others I couldn't say.
> 
> My SP has the same limitation. There are virtually no DOMs that implement the "parse with context" notion.
> 
> I suppose some kind of brute force workaround would be to try and manually pull in namespaces, but that's somewhat tricky to do in general if the fragment can be signed, though that's not a concern here.
> 
> -- Scott
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


-- 
The information transmitted in this email is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or 
other use of, or taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is prohibited. If you 
received this email in error, please contact the sender and permanently 
delete the email from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170410/0676babf/attachment.html>