More detail documentation needed for TLS configuration




12 years ago
4 years ago


(Reporter: bugs, Unassigned)





12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070309 Firefox/
Build Identifier: 3.0

In the LDAP authentication configuration you have the option of using ldaps or TLS in order to secure your authentication.  However the two are mutually exclusive.  I'd like to see some info added to the documentation that explains that when TLS is turned on, the ldap server string should not contain the protocol.  Also, this same info should be added to the edit parms panel for LDAP so that it is obvious when turning on TLS. Something like "Note: When using TLS for security, do not specify a protocol in the LDAP server string above."

Reproducible: Always

Steps to Reproduce:
1.View LDAP configuation panels and documentation
Actual Results:  
You will not see any details about TLS config

Expected Results:  
You will see more details


12 years ago
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 3.0

Comment 1

9 years ago
manu, can you confirm?

Comment 2

9 years ago
(In reply to comment #1)
> manu, can you confirm?

I'm slightly surprised to head that you shouldn't specify the protocol when using LDAP with TLS. While I've never used it in practice (I mainly keep to ldaps), looking at the code, I don't see anything that could justify this. Reporter, what made you arrive at that conclusion?

As for the boarder problem (the fact that there's little documentation for the use of TLS), there's really little to say. Looking at the Net::LDAP documentation, it should really be as simple as activating the option.

Comment 3

5 years ago
Can anyone please help me what exactly the bug is ?? I didn't get this. Also please provide me with the link of the bugzilla documentation.

Comment 4

5 years ago
Nitika: as for any Bugzilla documentation.
WONTFIX per comment 2.

Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.