Closed RichardMore closed 1 year ago
Hello Richard, It seems that you are talking about the timeout of the Windows login page, which is managed by Windows itself. The ldap-time-limit has nothing todo with your issue (it's the timeout used during AD/LDAP synchronization connection).
Check this link for information about changing the screen inactivity timeout for Windows 10 : https://stackoverflow.com/questions/39864379/how-to-change-windows-10-login-screen-inactivity-timeout
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI
DWORD Value: IdleTime
Unit: msec
Hi, You are right it was probably a Windows issue, but not with that registry key. Server 2012R2 had some issues that an upgrade to 2019 fixed. Thank you for your help!
Hi, I am trying to have a 60 second timeout for the Windows MFA login, I have in the registry timeout set to 60, on the server I have multiotp -config ldap-time-limit=60 as well but still closes the RDP connection after 30 seconds. Am I missing a setting somewhere?
Thank you for your help in advance!
version: 5.9.3.1 both server and cred provider