New user authentication failure

General
, ,
1

Hi All

Created a test account local to the VDA which is currently failing authentication when logging in via ThinLinc (web and client), despite working correctly for SSH and XRDP?

Alma 9.8
Thinlinc 4.20.1

error message is “login failed. Wrong username and password”

checked /var/log/vsmagent.log

Any tips and pointers would be appreciated.

Thanks

Harj

2

Hi,

Authentication in ThinLinc is handed off to the underlying operating system via PAM, so you should be able to use the same credentials as when logging in via SSH. Is there anything in your system logs to indicate why authentication failed?

3

Aaron,

Thanks for the ply .. Is there any specific group that the user needs to be a member of ? I’d assumed that if it could ssh and rdp onto the VDA without issues Thinlinc would just work.

Any pointers (logs) would be great to get this resolved as I’m far from a Linux admin.

Update:

Deleted the new user account - it was unable to login to the local VM console.
Created a new local user account - added to the wheel usergroup, able to login to the console, ssh and XRDP but not thinlinc.

Harj

4

Hi,

If you’re able to authenticate using SSH, then you should be able to authenticate using the same credentials with the native ThinLinc client. It’s the same mechanism for both.

Please check your system logs for details. You can run something like this on the server, before attempting to connect with the ThinLinc client:

journalctl --follow

You could also try increasing the debug level of the client by passing the -d5 argument at the command line when starting it:

You can find the resulting log file here:

1 Like
5

Aaron… thanks for the pointers. I’ll keep you posted on how I get on and hopefully, its a trivial issue.

1 Like
6

Just in case you happen to be using the browser client and authenticating against Active Directory, please see the following page:

7

Issue resolved .. my bad .. user error.

I failed to create the local user accounts on the broker server and thus the authentication failure. No issues with additional local accounts logging in via ThinLinc.

Next step is to adjoin the Broker(s) and VDAs and let AD DS manage authentication.

@ Aaron many thanks for tips on getting this fixed.

2 Likes