You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, xrdp can know if sesman could create a new session or find an existing session but cannot know the reason Due to this limitation, #642 will occur. Returning the result or reason to xrdp is very good to provide the exact reason of failure to users. It also helps to implement IP ban (fail2ban, blacklistd).
Maybe the following reasons are required at least.
authentication failed
user password expired
exhausted sessions count
user not in the TerminalServerUsers group
failed to execute backend
ex. Xvnc, X11rdp, Xorg executable doesn't exist
The text was updated successfully, but these errors were encountered:
An extra method auth_uds() is added to the PAM module to
allow a 'struct auth_info' to be created for a UDS login. The PAM stack
is used to check the UDS user can be authorized.
Also, an error code is returned from the auth module rather than a
simple boolean. This allows a more complete status to be communicated
to the user. See neutrinolabs#1921
and also neutrinolabs#909 and neutrinolabs#642
An extra method auth_uds() is added to the PAM module to
allow a 'struct auth_info' to be created for a UDS login. The PAM stack
is used to check the UDS user can be authorized.
Also, an error code is returned from the auth module rather than a
simple boolean. This allows a more complete status to be communicated
to the user. See neutrinolabs#1921
and also neutrinolabs#909 and neutrinolabs#642
An extra method auth_uds() is added to the PAM module to
allow a 'struct auth_info' to be created for a UDS login. The PAM stack
is used to check the UDS user can be authorized.
Also, an error code is returned from the auth module rather than a
simple boolean. This allows a more complete status to be communicated
to the user. See neutrinolabs#1921
and also neutrinolabs#909 and neutrinolabs#642
Currently, xrdp can know if sesman could create a new session or find an existing session but cannot know the reason Due to this limitation, #642 will occur. Returning the result or reason to xrdp is very good to provide the exact reason of failure to users. It also helps to implement IP ban (fail2ban, blacklistd).
Maybe the following reasons are required at least.
TerminalServerUsers
groupThe text was updated successfully, but these errors were encountered: