We have a similar setup (though possibly for poor reasons), with two different metadata files -- each with its own entity IDs defined -- running against the same IdP installation.<div><br></div><div>For us, the authentications transfer over across the entity IDs. That is, I log in for SP1 against IdPEntityID-A, and then I'm able to log into SP2 against IdPEntityID-B with no login challenge at the IdP. Again, there's only one IdP, it's just accessed via two distinct entity IDs. I can't tell from your post if this is the same situation you have, or if you actually have two IdP installations.</div>
<div><div><br></div><div>--- Eric<br><br><div class="gmail_quote">On Wed, Feb 8, 2012 at 9:36 AM, Christopher Bland <span dir="ltr"><<a href="mailto:chris@fdu.edu">chris@fdu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello all,<br>
<br>
I am trying to propose a solution to my superiors but am unsure if
it is possible. I would appreciate a sanity check. I have two
seperate IDPs (IDP-A & IDP-B). Each has its own unique entity
id which it uses to service SPs. I want to associate specific SPs
with IDP-A and others with IDP-B, these associates are exclusive to
each IDP. If IDP-A & IDP-B are using Terracotta to share
session info. My question is this, is there any way for a user to go
from a SP serviced by IDP-A to a SP serviced by IDP-B without being
forced to reauthenticate because the _idp_session cookie does not
match IDP-B's hostname and vice versa?<br>
<br>
Thanks in advance,<br>
<br>
-Chris<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
<div>-- <br>
<div>
<table border="0" cellpadding="0" cellspacing="0" height="125" width="530">
<tbody>
<tr>
<td valign="top" width="150"><img alt="fdu
logo" height="62" width="140"></td>
<td>
<div>Christopher Bland</div>
<div>Systems Manager<br>
Information Systems and Technology</div>
<div> <strong>1000 River Road, Teaneck NJ
07666</strong><br>
Mail Stop: T-BH1-01<br>
<img alt="phone" height="10" width="13">: <a href="tel:201-692-2414" value="+12016922414" target="_blank">201-692-2414</a> |
<img alt="fax" height="13" width="15">: <a href="tel:201-692-2494" value="+12016922494" target="_blank">201-692-2494</a> | <img alt="email" height="11" width="12">: <a href="mailto:chris@fdu.edu" target="_blank">chris@fdu.edu</a> </div>
</td>
</tr>
<tr>
<td colspan="2">
<div>"Fairleigh Dickinson University will
never<br>
ask for your
password. Please do not share it with others!"</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</font></span></div>
<br>--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br></blockquote></div><br></div></div>