<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm running the Koha OPAC on port 3333 on my website, and the Intranet on port 3334. Unfortunately (if I understand the rules for cookies correctly) it's not possible to have a cookie segregated to a certain website and a certain port number.</blockquote>
<div><br>This is correct. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
As a result, I can't login and access both the Intarnet and OPAC site on the same browser. For instance if I login as "kohaadmin" on the Intranet (port 3334), then login as "adams" on the OPAC (port 3333), the first cookie will be overwritten, and the Intranet site will complain that I'm now logged in as a non-administrative user (adams).<br>
</blockquote><div><br>A possible workaround for this is to give adams superlibrarian rights.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Right now, I've taken to accessing the Intranet on Firefox and the OPAC on MSIE to keep my logins separate. But could this problem be solved if Koha used different cookie names for the two different sections? e.g. instead of using CGISESSID everywhere, maybe use KOHAINET as the cookie name for the Intranet and KOHAOPAC for the OPAC site?<br>
<br>
Is this worth submitting an enhancement request over?</blockquote><div><br>Possibly, but the usual solution would be vhosts (<a href="http://staff/">http://staff/</a> would be your intranet, <a href="http://opac/">http://opac/</a>, your OPAC).<br>
</div></div><br>-- <br>Jesse