Please note that I have not tried to set something like this up, but I
think I might prefer a proper SSO solution to reduce the fragility, but
this is just my 2 cents.
First, in order to use the same cookie for both sling instances, the cookie
domain and path must be sent by the server from both
I'm going to start talking and saying things, and if I come across like I'm
being pedantic I apologize in advance :)
First, when we talk about logging in, we're talking about cookies. A cookie is
used to identify a Session or store user credentials. You can't have a server
side session or
Hi Ruben,
If you are logged in to your sling CMS is it to author content? If so, how
do you maintain consistency when load balancing across two nodes?
If you are not authoring, is the session to authenticate custom CMS
extensions to sing? In such scenario general advice seems to be
externalising
Jason,
sorry, I should have been clear about what I am looking for
1 apache server, 1 domain name (say cms.example.org)
2 sling instances (either on 2 servers or 2 different ports)
from a user point of view I'd like to log in to cms.example.org and be
fully logged in to both sling instances
Hi Ruben,
Can you clarify some, when you say two tenants, is this two separate domains ?
And when you talk about being logged in, are yu controlling access or just
validating that someone is logged in or not, i.e. being able to access
information based on a user id.
- Jason
On Sun, Dec 2,
