[WG: Sakai QA] [Building Sakai] Multiple Sakai instances - same browser?

[Kusnetz, Jeremy]

We had a similar experience with people hitting different instances of Sakai in the same browser.  The default cookie was getting overwritten when you logged into the 2nd instance knocking you out of the 1st.

You can add to your property file:

cookieName={Custom Sakai Instance Cookie Name}

Just make it a different cookie name for each instance and you should be good to go.


From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Sam Ottenhoff
Sent: Wednesday, December 19, 2012 2:24 PM
To: Neal Caidin
Cc: sakai-qa at collab.sakaiproject.org QA; sakai-dev Developers
Subject: Re: [Building Sakai] [WG: Sakai QA] Multiple Sakai instances - same browser?

Firebug for Firefox is highly recommended: getfirebug.com<http://getfirebug.com>

Your issue is to be expected, and is not a bug and is not new.  Sakai sets a cookie with name JSESSIONID to maintain your session. The cookie is not differentiated on a per-port basis thus the two servers continue to overwrite the other's JSESSIONID cookie.

--Sam

On Wed, Dec 19, 2012 at 2:18 PM, Neal Caidin <nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>> wrote:
For my test, yes, same domain.

2.9.x server - http://nightly2.sakaiproject.org:8087/portal

trunk server - http://nightly2.sakaiproject.org:8082/portal

If you provide steps I can check cookies. I imagine Firefox has some good dev tools for that?

Thanks,
Neal

On Dec 19, 2012, at 2:11 PM, Sam Ottenhoff <ottenhoff at longsight.com<mailto:ottenhoff at longsight.com>> wrote:


What are the steps to replicate?  What cookies are being set?  Are you using two instances on the same domain?

On Wed, Dec 19, 2012 at 1:36 PM, Neal Caidin <nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>> wrote:
Hi All,

At least a couple of us are running into an issue of trying to do some testing and using different instances of Sakai in the same browser, but it seems to be causing timeouts, so it is unusable. I don't think it has always been this way? Is this expected behavior or should a Jira ticket be opened?

One Use case is to replicate a Jira issue in 2.9.x server while confirming it is fixed in trunk.  For a workaround one can use two different browsers, though it might not be quite as convenient.

Maybe it is not that big a deal.

Thoughts?

Cheers,
Neal


_______________________________________________
sakai-qa mailing list
sakai-qa at collab.sakaiproject.org<mailto:sakai-qa at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org<mailto:sakai-qa-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"



This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20121219/269b64fc/attachment.html