MarnickTelenet
Programmer
Situation: a VB.NET-application that runs in a Windows-domain on a Citrix/Terminal-server
Frustration: users have to log-in twice: once in Windows domain and once in our application
Objective/goal: users that already are logged-in in Windows domain don't get the log-in screen of our application, because the system already knows who they are.
I think this is what we have to do:
1. Take the VB-object that can "look" in Windows active-directory (AD). From now on I call this object winADo.
2. Ask winADo the windows-username and look if this user-name is in the application usertable (table with the application users).
3. If so, you know the application user and don't have to start up the application log-in screen. Don't re-ask username and password. Done!
4. If not so, start up the application log-in screen to ask username and password.
5. If username/password found in application usertable, start-up the application.
6. If username/password not found in application usertable, say "wrong username/password".
Conclusion:
If user logs-in from the domain, he won't be re-asked for login/password, unless the user is not in the application usertable.
If user logs-in from extern (not in the domain), he has to give username and password in the application login-screen.
Question:
Does a winADo-object exists and if so, where can we find information about that?
Frustration: users have to log-in twice: once in Windows domain and once in our application
Objective/goal: users that already are logged-in in Windows domain don't get the log-in screen of our application, because the system already knows who they are.
I think this is what we have to do:
1. Take the VB-object that can "look" in Windows active-directory (AD). From now on I call this object winADo.
2. Ask winADo the windows-username and look if this user-name is in the application usertable (table with the application users).
3. If so, you know the application user and don't have to start up the application log-in screen. Don't re-ask username and password. Done!
4. If not so, start up the application log-in screen to ask username and password.
5. If username/password found in application usertable, start-up the application.
6. If username/password not found in application usertable, say "wrong username/password".
Conclusion:
If user logs-in from the domain, he won't be re-asked for login/password, unless the user is not in the application usertable.
If user logs-in from extern (not in the domain), he has to give username and password in the application login-screen.
Question:
Does a winADo-object exists and if so, where can we find information about that?
