As a matter of fact, I'm working on that right now...
In our situation there's an AD server in headquarters and we want members of it to be able to access our local farm. The easy way would be to establish Trust but between the
dingbats overworked staff at our end and the mindless bureaucrats directory administrators in HQ, that could be months away.
You can set up an Active Directory Membership provider with forms authentication as per:
However, that LDAP connection string won't work in its own as the HQ server won't bind to any old anonymous query (unlike our LDAP server, but that's getting turned off), so I have to provide a username and password, but I did find:
System.Web, Version=18.104.22.168, Culture=neutral,
I'm about to give this a try.
However there is one huge problem here!
From what I can see, my login credentials are going to be sent in the query in plaintext, which can't be good. I don't know much about LDAP:// style connections but back in my VBScript days the LDAP object was supposed to be able to do encrypted queries, but it wasn't implemented yet. That may be different now. Perhaps a more enlightened .net person can tell us.