Joint SP configuration for two applications- attributePrefix conflict

[Klingenstein, Nate]

I forgot to mention that you also need to ensure the SP's running use a shared session store.  Otherwise, the user would show up with a cookie just fine, but the lookup for the corresponding session would fail.

You have several options for doing that.  This might help.

https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPClustering

A lot of the warning verbiage here refers to a coherent application with a defined session management mechanism.  In that case, you would almost always want to rely on the application's sessions.

But, here, you have two different applications, and making the applications figure out how to share sessions is probably the more painful route by an order of magnitude.

On Nov 23, 2016, at 9:15 PM, Klingenstein, Nate <nklingenstein at calstate.edu<mailto:nklingenstein at calstate.edu>> wrote:

And you make the cookie in a sub-domain(or domain) that both can see, yes.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161124/c6a052ee/attachment.html>