----- Original Message -----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Heyho guys,
since nobody responded to my mail I sent on the 7th of February I'd like to bring that topic up again.
While I'm totally agreeing with you that there are other important problems to solve, I consider the lack of a proper login in bigger networks a major showstopper for your project. It can only be of your interest, that people in a LDAP/AD configuration with usernames like DOMAIN\USER are able to use your services. I pointed out, that it's probably just a few fixes away from a solution.
I'm understanding that your test case focusses on local users in some kind of databases, but however... I hardly see this as a "normal environment" in every company or organization which might want to use x2go. Really nobody is using local user databases on some Linux machine for storing user information and accounts except for Bob and Alice maybe.
If any of you likes to investigate this issue I can provide an writable x2go server and a domain account to test things out and find fixes for that.
Best regards
Robert
Robert,
as John has mentioned we use LDAP with AD in our environment. The local/central database holds details pertinent to the session state eg. mounted shares; whereas the authentication is performed against whatever you have configured in PAM. Have you integrated Linux authentication with AD yet ?
Thanks, Phil