Libki / libki-server

Libki Server
Other
55 stars 28 forks source link

Patron can use computer wo logging in #214

Closed MagnusEnger closed 4 months ago

MagnusEnger commented 3 years ago

Describe the bug I have not seen this myself, but a library is describing the following: A patron's time is used up, and the computer reboots. The patron is able to continue using the web, by opening a browser, which will be "over" the Libki login form, hiding it. Is this a known problem, or something we need to investigate further?

To Reproduce Steps to reproduce the behavior:

  1. Let the time run out
  2. Let the PC reboot
  3. Open a web browser
  4. Observe the web browser hiding the Libki login, letting the user surf the web indefinitely

Expected behavior The Libki login is expected to be a modal, blocking any other actions by the patron on the computer

Desktop (please complete the following information): It sounds like they upgraded the Libki client to 2.2.1.0, to see if this solved the problem compared to the older version they were running, but it did not.

kylemhall commented 3 years ago

Hi @MagnusEnger!

This is often a function of the computer running the client being too slow to launch the Libki client.

I would recommend taking a look at the disableInput feature which may help you: https://github.com/Libki/libki-client/blob/0b9df3508a092c34e5323a832b023f1e9cb81782/example.ini#L45

The most fullproof fix is to have Libki start as the user shell, and launch the Windows Explorer on login. You can find details about that here: https://github.com/Libki/libki-client/issues/39

kylemhall commented 3 years ago

Another thing you can look at is simply disabling as many Windows startup items as possible, to allow the Libki client to load more quickly.

bruzona commented 3 years ago

We encountered this issue a few years ago, and took a slightly different approach.

In our case, even when Libki was the ONLY​ startup item, yet users were able to "hijack the browser" prior to Libki client loading.)

Windows has an annoying feature (in this situation) where startup programs are INTENTIONALLY delayed, based on Microsoft's presumption that all users must want Windows to load first

This feature causes a delay in Libki loading, giving the user the opportunity to bypass.

This feature can be turned off with a simple registry edit. Details: https://thegeekpage.com/startupdelayinmsec/

  path: HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize
  name: StartupDelayInMSec
  data: 0
  type: dword

What this accomplishes is cause Windows to no longer delay startup programs, including the Libki client.

You can also disable through group policies, but in our situation we have not found it to be necessary, (and too often need task manager for our own purposes), and we use Libki in small sites where it is easy enough for staff to keep an eye on the handful of patrons.

[https://thegeekpage.com/wp-content/uploads/2019/02/explorer-new-key-regedit-min.png]https://thegeekpage.com/startupdelayinmsec/ Make Windows 10 Load apps fast during startup in windows 10https://thegeekpage.com/startupdelayinmsec/ Once the Windows 10 Os starts, a 10 seconds delay is by default set. This 10 seconds delay is provided so that the system perform important system tasks before loading desktop apps which starts eating memory.But, if you have a PC with Good Configuration, preferably SSD drive , then you may disable this delay and speed up the startup process of Windows 10 Computer. thegeekpage.com  


From: Kyle M Hall @.> Sent: Tuesday, August 17, 2021 8:02 AM To: Libki/libki-server @.> Cc: Subscribed @.***> Subject: Re: [Libki/libki-server] Patron can use computer wo logging in (#214)

CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders.

Another thing you can look at is simply disabling as many Windows startup items as possible, to allow the Libki client to load more quickly.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/Libki/libki-server/issues/214#issuecomment-900376742, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEVULGQQEJ66IPL246Q7PWTT5J2YFANCNFSM5CHJS4IQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

kylemhall commented 3 years ago

@bruzona that's fantastic info! Thanks for sharing. I think I may find some place in the manual to add that.

kylemhall commented 2 years ago

@MagnusEnger were you able to solve your issue?

fclibtech commented 2 years ago

Hi, Please check Scheduled Tasks under Admin login, there may be an MS Edge update process running at each login. This made MS Edge appear over the top of the Libki login screen at our library branches. Remove the trigger for "at log on of any user"

image

sekjal commented 4 months ago

Lots of good stuff here... going to mark this one as closed

kylemhall commented 4 months ago

The solution we've been using has been to set Libki as the login shell instead of explorer. Then on login Libki will launch explorer.exe

It isn't the only alternative you'll find though. I know there is at least one other discussion going on here in the Libki issues with yet another solution!