Table of contents
No headers
Here is a write up on how to integrate with ADAM authentication. This form of authentication commercially supported.
Use the built in Microsoft Active Directory Authentication service but alter a few keys to suit.
bindingdn: cn=$1,cn=users,cn=xxxxx,dc=xxxxxxxxx,dc=com [Different to standard AD]
To limit the amount of searching specify the search location as the actual CN where the users are kept in the ADAM database, but I think this is optional.
userquery: CN=$1 [Different to standard AD]
This is the same as OPENLDAP as the users in ADAM, in this example configuration, don’t have the property samAccountName
hostname: servername.com:9381 [ADAM listening port is not standard so direct it with the :portnumber on the end of the server fqdn entry]
searchbase: CN=xxxx,DC=xxxxxxxxxxxxxx,DC=com
We limit the searchbase to the specific location in the ADAM structure.
groupmembersattribute: memberOf [This is an additional key to enable group membership resolution]
One thing that must be remembered is that ADAM only allows simple binds, and some alterations to the ADAM instance might be needed to make this work.
I ended up with an ADAM preconfigured by another party and did not have to make these changes as I suspect they did this already to support their own application.