Joint SP configuration for two applications- attributePrefix conflict

[Klingenstein, Nate]

IsPassive has always been reasonably well supported by IdPs, the problem is the application end and the error handling there.

Well, my favorite:

https://docs.microsoft.com/en-us/azure/active-directory/active-directory-single-sign-on-protocol-reference

IsPassive       optional        If provided, this should be false. Any other value causes an error.

I might be able to find an IdP in InCommon that doesn't support isPassive correctly.  Maybe even two.

If you can make this work reliably, go for it.  My only addition is that isPassive and one or two entityID's are not mutually exclusive options.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161129/d0374fcd/attachment.html>