Closed Bug 392212 Opened 18 years ago Closed 18 years ago

LDAP parameters descriptions should mention how to use SSL connection

Categories

(Bugzilla :: Documentation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 3.0

People

(Reporter: timello, Assigned: sam.folkwilliams)

Details

Attachments

(2 files, 1 obsolete file)

When trying to use LDAP with SSL (636 port) Bugzilla has returned 84 LDAP error which is LDAP_DECODING_ERROR. After changing the used module from Net::LDAP to Net::LDAPS in Bugzilla/Auth/Verify/LDAP.pm it became to work correctly. The Net::LDAPS documentation says that all methods from Net::LDAP can be used with this module, so I would suggest to change that module for Net::LDAPS.
Attachment #276652 - Flags: review?(mkanat)
Assignee: administration → timello
Attachment #276652 - Attachment is obsolete: true
Attachment #276656 - Flags: review?(mkanat)
Attachment #276652 - Flags: review?(mkanat)
Status: NEW → ASSIGNED
Did you test that this still works without SSL? I'm pretty sure that Net::LDAP automatically uses SSL if you specify an ldaps:// URL. Perhaps that should be mentioned in the parameter description, though.
(In reply to comment #3) > Did you test that this still works without SSL? > > I'm pretty sure that Net::LDAP automatically uses SSL if you specify an > ldaps:// URL. Perhaps that should be mentioned in the parameter description, > though. > You are right. ldaps:// works. So, changing the bug summary.
Severity: normal → enhancement
Summary: Bugzilla LDAP support does not work over SSL connection → LDAP parameters descriptions should mention how to use SSL connection
Component: Administration → Documentation
OS: Linux → All
Hardware: PC → All
Comment on attachment 276656 [details] [diff] [review] Missing some changes. r- per previous comments.
Attachment #276656 - Flags: review?(mkanat) → review-
The doc sort of mentions this, but I agree it could be more clear in regards to SSL specifically: -- You can also specify a LDAP URI, so as to use other protocols, such as LDAPS or LDAPI. If port was not specified in the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS' schemes respectively. Ex. "ldap://ldap.company.com", "ldaps://ldap.company.com" or "ldapi://%2fvar%2flib%2fldap_sock" --
Assignee: timello → sam.folkwilliams
Severity: enhancement → normal
Status: ASSIGNED → NEW
Docs patch - explain lpadi, ldaps and add a <tip> for ldaps
Attachment #303904 - Flags: review?(documentation)
Comment on attachment 303904 [details] [diff] [review] docs patch for lpaps and lsapi - schemes respectively. + schemes respectively. This adds a space at the end of the sentence, right after the period. Could it be removed?
(In reply to comment #8) > (From update of attachment 303904 [details] [diff] [review]) > - schemes respectively. > + schemes respectively. > > This adds a space at the end of the sentence, right after the period. Could it > be removed? > This can be removed on checkin i'd imagine
Status: NEW → ASSIGNED
Comment on attachment 303904 [details] [diff] [review] docs patch for lpaps and lsapi Looks good to me. r=LpSolit
Attachment #303904 - Flags: review?(documentation) → review+
Flags: approval3.0+
Flags: approval+
Target Milestone: --- → Bugzilla 3.0
tip: Checking in docs/en/xml/administration.xml; /cvsroot/mozilla/webtools/bugzilla/docs/en/xml/administration.xml,v <-- administration.xml new revision: 1.90; previous revision: 1.89 done 3.0.4: Checking in docs/xml/administration.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/Attic/administration.xml,v <-- administration.xml new revision: 1.70.2.13; previous revision: 1.70.2.12 done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: