Hi,
I had a plan to authenticate users via AD.
The plan was to add code to EDBEngineServerSessionLogin where it first checks if the user is in the form of Username@domain.local or domain\username,
Then I check if the user can login to the domain with the username and password via Windows API (LogonUser)
If it passes, I update the EDB user with the password provided and set AllowLogin to true in EDBEngineServerSessionLogin .
My problem is that the name field in Configuration.users does not support @ or \. A workaround can then be, if username was passed by reference, to change the username in EDBEngineServerSessionLogin, I can then link an EDB user to a domain user in the attributes of the user and change the Domainusername to the name of the EDB user in EDBEngineServerSessionLogin at login.

Unfortunately this cannot be done. Is there some other way to do custom authentication? Can the fieldtype of the name field in configuration.users be changed?

Thank you!

Thank you!

Hoken,

<, I had a plan to authenticate users via AD.
The plan was to add code to EDBEngineServerSessionLogin where it first checks if the user is in the form of Username@domain.local or domain\username,
Then I check if the user can login to the domain with the username and password via Windows API (LogonUser)
If it passes, I update the EDB user with the password provided and set AllowLogin to true in EDBEngineServerSessionLogin .
My problem is that the name field in Configuration.users does not support @ or \. A workaround can then be, if username was passed by reference, to change the username in EDBEngineServerSessionLogin, I can then link an EDB user to a domain user in the attributes of the user and change the Domainusername to the name of the
EDB user in EDBEngineServerSessionLogin at login. >>

How about just converting any special characters in the user identifiers into underscores ?  As long as you do it the same way every time, it will work without issue.

We have a customer that has been performing AD logins using this method for some time (it was the reason for the OnServerSessionLogin event in the first place).

Tim Young
Elevate Software
www.elevatesoft.com

Hi,
so when would that conversion take place? The username cannot be changed in the ServerSessionLogin event, so it will have to take place on the client side before connection (as I do now)?
Handling this seamlessly on the server side would nice...