Http Session management in multiple publish instances

[chinthakasuse]

Hi Guys, has someone worked on AEM session management on publish instances. (http sessions in the publisher without sticky sessions or reverse replication). I know AEM architecture is designed in a stateless manner. I am doing a POC for a client. They want to know all the options. If it is possible what options we have and what drawbacks in that approach.

In short they want to keep user information in a storage ( eg: Redis cache - Azure. They want to communicate directly with publish instances having kept user sessions at publish instance level. So this request doesn't come via dispatcher. They don't want to save user info on client end too. It has to be a server cookie according to their requirement.)

Please let me know if anyone has a good solution for this.

[Jörg_Hoh · Accepted solution]

You can use HTTP sessions; in order to share the sessions you need enable HTTP Session replication. The embedded jetty does not support this, but you can use Tomcat and use the WAR deployment. You can configure tomcat for HTTP Session sharing, although I don't know if tomcat supports redis for that.

Jörg

[chinthakasuse]

Hi Jörg, I am extremely sorry for this late reply. Thanks for your answer mate. I am still checking few options here.I will have a look on your suggestion too. Thanks. Regards, Chinthaka