on 09-20-2012 3:32 PM
Hello,
I did set up the following environment:
I did not get a result. The Common Name RDN is still the samAccountName of the user.
Questions:
Best Regards,
Markus Nüsseler-Polke
Hi Markus,
here my answers.
Question 1
Exist a logfile where I can find information, what goes wrong with the LDAP search?
Answer: Yes, activate trace in Secure Login Server and start tracing using Security Troubleshooting Wizard (in AS JAVA - nwa), or if you are more familar with, use network sniffer tools.
Question 2
Which search string is used by the SLS (userPrincipalName or samAccountName)?
Answer: User ID (comparing to your question: samAccountName) will be used and will be searched in BaseDN (LdapReadBaseDN). Secure Login Server is able to distinguish the differences between ADS System and LDAP System.
Question 3
Which attribute is used to search? If an openLDAP is used, then the attribute 'uid' should be used for the search.
If a Microsoft AD is used, then the attribute 'userPrincipalName' should be used. Can this be configured?
Answer: From my point of view this is not necessary, as we are using User ID and search in the BaseDN. So it works for both. Maybe you want to provide an example configuration?
Best regards,
Frane
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.