What version are you running?
1.7.7.1
What's the URL of the page containing the problem?
admin/settings/authentication/
What steps will reproduce the problem?
1. In the upper part of the form unset the "Allow anonymous read-only access" mark
2. Go down the form filling ldap-related fields
3. Bump into the Anonymous User Mask, and Password.
What is the expected output?
I've expected the explanation who is this Anonymous, why he has a password (anonymity is always free), and why these fields are still active if I've already prohibited them to use my system
What do you see instead?
No clear info found. You've just retyped the settings below.
I'm using several other tools with LDAP auth, so I could guess what you mean. I suggest renaming these unclear setting to the following ones:
*********
Manager DN {instead of anonymous}
*********
Help for this item:
*********
If your LDAP server doesn't support anonymous binding (IOW, if your LDAP server doesn't even allow a query without authentication), then Jenkins would have to first authenticate itself against the LDAP server, and Jenkins does that by sending "manager" DN and password.
A DN typically looks like CN=MyUser,CN=Users,DC=mydomain,DC=com although the exact sequence of tokens depends on the LDAP server configuration. It can be any valid DN as long as LDAP allows this user to query data.
This configuration is also useful when you are connecting to Active Directory from a Unix machine, as AD doesn't allow anonymous bind by default. But if you can't figure this out, you can also change AD setting to allow anonymous bind. See this document for how to.
*********
Or at least a part of this.
*********
Manager Password
*********
Explanation for this field:
*********
Password for the manager DN specified above.
*********
What operating system are you using? What browser?
Debian 6.0, MySQL 5.1, browser-independent issue.
