What does “active directory integration” mean in your .NET app?

Question

Our marketing department comes back with \"active directory integration\" being a key customer request, but our company does not seem to have the attention span to (1) decide on

Answer 1

from a administrators perspective i want a ad-integration to do the following things

1. never ever write back to the AD, i just don't trust 3rd party software in this point
2. being able to import users from AD

3. being able to set a security group eg "ApplicationXYZ Users" to be used for software distribution and rights (shared folders, ...) if necessary but this should obey number 1., so the admin creates the security group and tells the appserver which one it is.

4. single sign-on (makes it easier for the users cause they only need to know their windows login, and enforces the domain wide password policy)

5. a deactivated AD-User, or a AD-User that is no longer in "ApplicationXYZ Users" should not be able to login

6. link AD-Group to Application Group but that would be optional, i really can life without that

hth