non cluster IdP behind hardware load balancer
Chad La Joie
lajoie at shibboleth.net
Mon Apr 2 19:16:27 BST 2012
First, upgrade to a supported version of the IdP.
Then, make the configurations of the twp IdPs identical.
Lastly, configure you load balancer to send traffic to only one server
and failover to the other one.
On 4/2/12 2:04 PM, Jean Robertson wrote:
> Hello,
>
> We are looking for a non-cluster pair of IdP's behind a hardware load
> balancer.
>
> The only reason we want it behind a load balancer is a fast recuperation in
> case of failure.
>
> We are not looking to share load between servers.
>
> We are planning to have a single IdP server run for long periods of time and
> should it fail, the standby would take over.
>
> We know that single sign on is lost in this case.
>
> We are using shibboleth IdP 2.1.5 software
>
> My question:
> - how to configure this?
>
> Do we call the AnonymousRelyingParty and DefaultRelyingParty the same in each
> IdP's relying-party.xml config file? (The name being the one that the front
> end is called)
>
> Do we copy the SHIBHOME/credentials cert and key from one machine to the
> other?
>
> Is there something I missed apart from these steps?
>
> I did look for documentation but did not quite find what is being proposed
> here.
>
> Thanks,
>
> Jean Robertson, McGill University
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list