If you are looking at this post, you would have already installed reviewboard and are facing issues configuring LDAP on it.
For others who landed here by chance:
Now comming to the topic, reviewboard asks for the following LDAP settings:
LDAP Server : ldap://<your server ip>:389 (By convention this can be : ldap://ldap.<your company name>.<com|net|org>:389)
LDAP Base DN (Used to perform LDAP searches) : Should generally be composed of OU & DC. For ex:- OU=users,OU=<US|Canada|AsiaPac|Japan>,OU=<(Engineering|Eng)|(Finance|Fin)),DC=<yourcompanydomain>,DC=<com|net|org>
example1: OU=users,OU=AsiaPac,OU=Eng,DC=GooG,DC=com
example2: OU=users,DC=CSCO,DC=com
User Mask: (sAMAccountName=%s) (This should generally do the trick if not try CN=%s or UID=%S. You can also refer to http://msdn.microsoft.com/en-us/library/windows/desktop/aa746475%28v=vs.85%29.aspx for more information)
If your LDAP server allows anonymous users to query then you can leave
Anonymous User Mask : <blank>
Anonymous User Passwrod: <blank>
if not then you may need to ask your network admin to create a team/group id which can browse LDAP server. But if you want to check if everything is configured well you can use your login credentials here.
Anonymous User Mask : <domain>\<your user name>
Anonymous User Passwrod: <your password>
Acronyms
DN : Distinguished Name
CN : Common Name
DC : Domain Component
SN : Surname
mail : mail
For others who landed here by chance:
Review Board is a powerful web-based code review tool that offers developers an easy way to handle code reviews. It scales well from small projects to large companies and offers a variety of tools to take much of the stress and time out of the code review process.You can checkout reviewboard @ http://www.reviewboard.org/
Now comming to the topic, reviewboard asks for the following LDAP settings:
LDAP Server : ldap://<your server ip>:389 (By convention this can be : ldap://ldap.<your company name>.<com|net|org>:389)
LDAP Base DN (Used to perform LDAP searches) : Should generally be composed of OU & DC. For ex:- OU=users,OU=<US|Canada|AsiaPac|Japan>,OU=<(Engineering|Eng)|(Finance|Fin)),DC=<yourcompanydomain>,DC=<com|net|org>
example1: OU=users,OU=AsiaPac,OU=Eng,DC=GooG,DC=com
example2: OU=users,DC=CSCO,DC=com
User Mask: (sAMAccountName=%s) (This should generally do the trick if not try CN=%s or UID=%S. You can also refer to http://msdn.microsoft.com/en-us/library/windows/desktop/aa746475%28v=vs.85%29.aspx for more information)
If your LDAP server allows anonymous users to query then you can leave
Anonymous User Mask : <blank>
Anonymous User Passwrod: <blank>
if not then you may need to ask your network admin to create a team/group id which can browse LDAP server. But if you want to check if everything is configured well you can use your login credentials here.
Anonymous User Mask : <domain>\<your user name>
Anonymous User Passwrod: <your password>
Acronyms
DN : Distinguished Name
CN : Common Name
DC : Domain Component
SN : Surname
mail : mail
Comments