[mitreid-connect] Multiple instances connected to a single DB

[Justin Richer]

Yes, you will need to replicate your session information, but that’s doable with Tomcat and other containers, and Spring should support it fine.

There’s no reason for introspection not to work in this configuration, so I’m not sure what you’re talking about there. I’ve seen several split deployments (multiple IdPs using multi-homed DNS and a common DB, no load balancer) and introspection works perfectly in those cases. Something else must be wrong if that broke.

 — Justin

> On Jul 6, 2016, at 6:49 PM, yannick.beot at gmail.com wrote:
> 
> Hi,
> It depends on your configuration but you should probably  use a sticky session or replicate session data between your instances.
>  
> Envoyé de mon téléphone Windows 10
>  
> De : Luiz Omori <mailto:luiz.omori at duke.edu>
> Envoyé le :mercredi 6 juillet 2016 22:42
> À : mitreid-connect at mit.edu <mailto:mitreid-connect at mit.edu>
> Objet :[mitreid-connect] Multiple instances connected to a single DB
>  
> Hi,
>  
> We have an use case that calls for having multiple servers running in parallel in a load balancing fashion. All instances would be connected to a single DB backend. Has anybody tried that? Any potential problems you can think of? We know that all of them will have to use the same ISSUER configuration otherwise, perhaps among other things, introspection won’t work (we tested).
>  
> Regards,
> Luiz
>  
> _______________________________________________
> mitreid-connect mailing list
> mitreid-connect at mit.edu
> http://mailman.mit.edu/mailman/listinfo/mitreid-connect

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/mitreid-connect/attachments/20160706/eb851f01/attachment-0001.html