[Building Sakai] Unexpected login prompts - Sakai 2.6.0

[Dave Ross]

Once you log in the second time, you'll have a valid session on both
Sakai servers and the problem will be "masked".

I would review your CSS config. Cookie-based persistence is the
de-facto standard around here - SSL Session based persistence should
work but I can't say it's as tried and true as cookie-based.

On Tue, Jun 15, 2010 at 4:03 PM, Grossman,John E
<john.grossman at mdanderson.org> wrote:
>
> We are running a CSS load balancer with two Sakai instances. The Sakai instances are not cluster aware.
> The CSS is configured for SSL sticky sessions as we use SSL for all traffic to Sakai. This is based on the SSL Session ID (not the Sakai session ID).
>
> We did suspect the load balancer, but the odd thing is that when you get this unexpected prompt to authenticate, you can generally re-enter your Sakai session with no problems. If the load balancer were sending you to the wrong server, it seems like you wouldn't be able to re-enter the Sakai session because the session would only exist on the original server. Am I misunderstanding Sakai sessions?
>
> John
>
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Zach A. Thomas
> Sent: Monday, June 14, 2010 5:16 PM
> To: sakai-dev at collab.sakaiproject.org
> Subject: Re: [Building Sakai] Unexpected login prompts - Sakai 2.6.0
>
> This is consistent with a cluster environment where the load balancer
> does not properly "stick" the user to a single server. Thus, they're
> logged in on one of the nodes, but the next request goes to some other
> server where they're _not_ logged in.
>
> Can you confirm whether you are running a cluster of app servers? And if
> so, how are you performing load balancing?
>
> cheers,
> Zach Thomas
> Owner, Aeroplane Software LLC
>
> On Sat, 2010-06-12 at 17:10 -0500, Grossman,John E wrote:
>> We periodically have a problem where a user is in the system working
>> (constant activity – not a timeout issue) and Sakai unexpectedly
>> prompts for user name and password. A variation on this is that Sakai
>> will prompt several times. The correct credentials are entered several
>> times and then the mangled screen shown shown below appears. The log
>> shows this:
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"