Summary: | Separate sessions for OPAC and intranet | ||
---|---|---|---|
Product: | Koha | Reporter: | Chris Nighswonger <cnighswonger> |
Component: | Authentication | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED WONTFIX | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | P3 | CC: | dpavlin, m.de.rooy, veron |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8010 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Chris Cormack
2010-05-21 00:32:46 UTC
Verified: Koha installation with different port numbers: Log in with user one in staff Log in with user two in OPAC Result: Login in staff has changed to same user as in OPAC. If user has no staff permissions, Login screen appears. Koha installation with different URLs: Log in with user one in staff Log in with user two in OPAC Result: Logins are independent See: https://tools.ietf.org/html/rfc6265#section-5.4 "Cookies do not provide isolation by port." That explains why installations where staff client and OPAC only differ by port number share the same login credentials. Workarounds with Firefox: - Open a new private window (it will have it's own cookies). That works great to have a staff user and a 'normal' user in two windows and/or have different language settings. (However, multiple private sessions will share the same cookies.) - Use a separate profile as described in: http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile Why not close this report? If you want to have separate sessions, use another ip address or domain name. People who want to have the shared cookie on the other hand, can use the two ports on the same domain. Everyone happy ? +1 to close I think closing this one would be ok - but there is an open issue: because we only have one session, it's not possible to set different time out times - the same pref is used for both staff and OPAC. It could still be desirable to separate the sessions to make this possible. (In reply to Katrin Fischer from comment #5) > I think closing this one would be ok - but there is an open issue: because > we only have one session, it's not possible to set different time out times > - the same pref is used for both staff and OPAC. It could still be desirable > to separate the sessions to make this possible. I opened bug 15428 for this specific enhancement request. Closing this bug now. |