Announcement Announcement Module
Collapse
No announcement yet.
Clustering Spring SAML Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Clustering Spring SAML

    Hi,

    We have a 2 node production cluster where the 2 nodes are sharing a single database. We are trying to implement Spring SAML and have confirmed it works on a single test server.

    We don't have any kind of session state sharing between the 2 nodes in the cluster, as we just use sticky sessions in the load balancer to keep each user stuck to one of the nodes. Would you think that Spring SAML would work in this kind of setup, or is there state between SAML http communications that needs to be shared between the two nodes?

    Also, if we implemented Spring Security session state sharing between the nodes would that help?

    thanks


    Steve

  • #2
    Hi Steve,

    As long as you don't require fail-over (only possible when sessions are replicated) and don't need to support IDP-initialzed Single Logout with SOAP binding (as these calls don't include sessionID and could end-up on any node) everything should work just fine.

    Brs, Vladi

    Comment


    • #3
      Hi Vladi,

      Great, thanks for that reply. Does it work in this situation because each client is stuck to a particular node using the load balancer's sticky session? Does that rely on the load balancer spotting the sessiodID in the GET/POST and making sure a particular sessionID only goes to one particular node?

      thanks


      Steve

      Comment


      • #4
        Yes, it works in this situation and it relies on sticky sessions. They must be in place for the SAML extension to work correctly in a clustered environment.

        V.

        Comment

        Working...
        X