Thank you for the suggestion.
I need to use their passwords in Active Directory to authenticate them though but I don't need to have an access to them. I just need those authenticated users through Active Directory and somehow define those in SQL so that I can still use the role/membership provider of asp.net in my app and have an external database with additional info on the SQL side.
--No idea how to handle and meet to the requirements on the asp.net's provider side though in SQL
Main Topics
Browse All Topics





by: tony_angelopoulosPosted on 2009-06-03 at 11:26:08ID: 24539569
What I would do is use ADAM.
/a/Using-V S/Making-S ense-of-AD AM/
http://www.devsource.com/c
you would want to create a stored procedure that queries your AD structure through ADAM and run it every day (as part of a package or command line script depending on your version of SQL). I don't have access to the code I wrote for my previous employer, but this is exactly what I did. ADAM has it's own strange query syntax, but you want to get that data piped daily into a new table. You can at least get to the username information this way. What I did was did a lookup to see if the currently logged on user was in this table, I would let the user pick a password. That's the caveat to using ADAM with this dual approach; you won't get access to their passwords. But at least at that point, you can find the user, add them via roles and membership, and let them pick their password.
I had the same problem! I wish I could get access to that sproc. Hopefully someone will have better information for you, but that's my 2 cents!