Validate User Against Active Directory
-
We have a medical device that is connected to the LAN but is not on Active Directory. The instrument is running Windows Embedded as a service. When a user logs into the device we want to validate them against AD. I've found plenty of example of validating users, but they all seem to assume that the code is being run under an account of an AD user. How to I validate a user against AD when the instrument isn't on AD?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
We have a medical device that is connected to the LAN but is not on Active Directory. The instrument is running Windows Embedded as a service. When a user logs into the device we want to validate them against AD. I've found plenty of example of validating users, but they all seem to assume that the code is being run under an account of an AD user. How to I validate a user against AD when the instrument isn't on AD?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
The device should able to connect AD to validate the user. Or you could create a web service that can connect to AD and let the medical device call that web service to verify the user.
-
The device should able to connect AD to validate the user. Or you could create a web service that can connect to AD and let the medical device call that web service to verify the user.
Keviniano Gayo wrote:
The device should able to connect AD to validate the user.
Unless someone logs into Windows on the device, it won't connect. Here's how I'm trying
using (var context = new PrincipalContext(ContextType.Domain, credentials.ServerName, credentials.UserName, credentials.Password))
{
validated = context.ValidateCredentials(userName, password);
}Again, this works if someone is logged into Windows. if not, it doesn't
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Keviniano Gayo wrote:
The device should able to connect AD to validate the user.
Unless someone logs into Windows on the device, it won't connect. Here's how I'm trying
using (var context = new PrincipalContext(ContextType.Domain, credentials.ServerName, credentials.UserName, credentials.Password))
{
validated = context.ValidateCredentials(userName, password);
}Again, this works if someone is logged into Windows. if not, it doesn't
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I see.. i haven't tried connecting to AD without logging into windows. I used the same code as above to verify the user in AD. Perhaps calling a custom web service to verify a user in AD would be the best route.