[Koha] Rotating IP Address and Koha Logout

[Barry Cannon]

Hi Charles,
              To temporarily get around this problem you can disable
the SessionRestrictionByIP
system preference in Koha. This binds the user's session ID to their public
IP address. If it changes, the session becomes invalid and Koha will prompt
for a new login.

The changing IP seems to be unrelated to AWS as they appear to be your ISP
addresses. Does the same problem exist outside of your organisation? For
example, at home or on a mobile device. If not then the problem is most
likely related to an outbound proxy at your end - your IT might look into
this. If it still happens elsewhere then perhaps your ISP is doing
something with transparent proxying that they might be able to help you
with.

Regards
Barry





<http://www.interleaf.ie/>


*Barry Cannon* Technical Director

 bc at interleaf.ie    +353-1-286-5855 <+353%201%20286%205855>  Ext: 102

 A98 YD30    www.interleaf.ie



On Tue, 5 Jul 2022 at 00:21, Charles Kelley <cmkelleymls at gmail.com> wrote:

> Hi, all!
>
>     My library is moving its Koha ILS to an AWS-based server. In
> development, it was on a standalone laptop.
>
>     In the testing phase on the AWS server, we have noted that the IP
> address for logins changes every thirty seconds and staff are signed out
> from Koha. The staff have to sign in anew and refresh. Whatever the staff
> were working on -- search, record editing, uploading new records, etc. --
> may or may not survive intact.
>
>     We don't know what causes this, but it's like
>
> IP 42.0.2.35
> Staff types a search query.
> IP 42.0.2.35
> Staff selects Edit Record from dropdown menu.
> Sudden change to IP 42.0.2.29
> Record vanishes.
> Login screen appears.
> New IP 42.0.2.34
> Staff logs in anew
> Staff backs up two tabs (or windows) and continues.
> New IP 42.02.31
> Repeat of what staff intervention at New IP 42.0.2.34
>
>     Eventually whatever the staff were working on is accomplished, but
> logging in anew and reentering the previous steps so often are a bit
> inconvenient, to state the least.
>
>     My IT staff doesn't understand this phenomenon. We checked the system
> preferences, but we haven't changed the timeouts since Koha was initially
> installed. Has this been reported to the Koha development teams or on this
> discussion group before?
>
>     Does anyone have an idea what would be causing this?
>
> --
>     よろしくお願いします。
>
>     -- Charles.
>
>     Until 2022-07-15:
>         Charles Kelley, MLS
>         PSC 704 Box 1029
>         APO AP 96338
>         +81-80-4356-2178 [JPN cell]
>
>     From 2022-07-18:
>         Charles Kelley
>         c/o Bob and Ronni DiGioia
>         147 Mitchel Drive
>         Oakland, MD 21550 USA
>         +1-301-741-7122 [US cell]
>
>     mnogojazyk at aol.com [h]
>     cmkelleymls at gmail.com [p]
>
>     linkedin.com/in/cmkelleymls
>     Meeting Your Information Needs. Virtually.
> _______________________________________________
>
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>