One of the developers would have to answer you as to exactly what is pulled in by the LDAP query. But if your new users are getting "personal" information populated upon login, the logical answer is that it is pulling it from the LDAP query.

We do not put that information into AD here, so I have not tested exactly what it does/does not pull in.

AFAIK the AD provider uses com interop to call the COM classes to integrate with AD (hence the need to use full trust) - this takes the necessary values from the settings you applied and internally builds up an LDAP query - the relevant code is in https://dnnauthad.codeplex.com/Source... -during login the authenticationcontroller.vb uses methods in that class to populate a userinfo class and then store that in the DNN database (authenticationcontroller.vb also optionally handles role synchronisation).

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Lu, read through the documentation on the codeplex site linked earlier for instructions to set it up. Basically the setup is done under Admin-Extensions and that's where you'll enter your LDAP settings. And what Cathal means by Full Trust is that your DNN site has to be running under Full Trust (it's a setting in the web.confg) for the provider to work.