load balancing 2 shibboleth IdP servers

Lipscomb, Gary glipscomb at csu.edu.au
Wed Aug 5 23:01:03 UTC 2020

Same here,
We use puppet to keep all our configurations in sync
Same configuration into devel then qa/uat then production. Full change control process.

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Joseph Fischetti
Sent: Thursday, 6 August 2020 03:09
To: Shib Users <users at shibboleth.net>
Subject: Re: load balancing 2 shibboleth IdP servers

>During upgrades we upgrade the passive site first, evaluate, then make
>it active.  Makes it easy to switch back to the old environment in case
>of any major showstoppers.

Does anybody have a good mechanism for keeping things in sync?  Things like attribute resolvers/filters and metadata providers?
I find myself testing in test, verifying, and then updating each of our prod servers and reloading their services one by one.  It's cumbersome and error prone. 

For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list