Ok, that would take some customization to support doing a lookup by
distinguished name first, and then using that record's sAMAccountName to bind
with. Are the distinguished names and sAMAccountName values so different that
you need to do that extra lookup? I mean, couldn't a user type in the DN
Hi Dave
Thanks for the reply
I am trying to use Windows AD as my LDAP server. Here is the scenario
1. Connect to AD with the pre-set user (which is "auth.ldap.admin_dn" ).
2. Query active directory with the pre-set user's credentials and search for
the distinguished name
3. based on the
Hello!
Our LDAP authorization module offers some configuration options, but not enough
to do what you want I think. Allura uses "auth.ldap.admin_dn" to bind in some
situations, but for validating and setting passwords, it uses the current user.
Does that not work for your LDAP setup? How would
1. When I use LDAP as my authentication method. The Allura sent user login
credential to LDAP instead of sent the "auth.ldap.schroot_name" I put in the
"development.ini" during Ldap bind request step. I think the user ID should be
send after bind request success.
2. When I use command
