[Deploying Sakai] Sakai + mod_jk and webservices

[Sam Ottenhoff]

>
> I'm tryin to execute login method of SakaiLoginPortal . The main problem
> is this:
>
> As we use mod_jk as load balancer,  after that we execute the login method
> to obtain a session id,  we redirect to sakai portal  using sakai.session
> as part of url. This value is not valid all time, because node 1 or node 2
> could not match with this session id (Depends of what node was response)
>
> My question is: That is the expected result. Or maybe there are a problem
> with sticky session?
>

It's the expected result if you are creating a session on one of two nodes
and then the user randomly lands on one of two nodes.

The easy solution: make sure you only create the session on only one node
and make sure the user only lands on that same node.  Use Apache rules to
send special URL paths to the same node every time.

The difficult solution: create a URL for the end-user that includes a
parameter that will make Apache route the user to the correct node.  For
example, if you create the session on node1, then the URL would look
something like
https://sakai.example.edu/portal/?sakai-session=xxxxxxxxx&JSESSIONID=xxxxxxx.node1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20150108/5baeb71a/attachment.html