Robert Markula wrote:
If I try to login via x2go to an account that's in the server's local /etc/passwd, everything works as expected.
But if I try to login via x2go to an account that's not in the server's passwd, but in ldap/kerberos, the x2go white login dialog disappears, but nothing else happens. Running x2go from a terminal, I get this output:
To put the above in other words: How can one get x2go to use an existing ldap/kerberos-server to authenticate the user?
I'm quite sure I once saw an environment where the x2go client used its own session management (no ldap-server set in the x2go client settings), but as the username and password was given from a user in ldap/kerberos, he could login and all worked smoothly. I was quite impressed back then to see how seamless x2go integrates in the existing authentication infrastructure.
I guess it was just a PAM issue on the x2go server machine, but I'm a bit lost at what has to be configured exactly.
Cheers, Robert