Bug 782617 - LDAP SSL support/implementation seems wrong
Summary: LDAP SSL support/implementation seems wrong
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration, Core Server
Version: 4.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 23:11 UTC by Larry O'Leary
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781621 0 unspecified CLOSED ldap ssl connections not working for JON 3.0.0.GA 2021-02-22 00:41:40 UTC

Internal Links: 781621

Description Larry O'Leary 2012-01-17 23:11:55 UTC
The LDAP SSL configuration options provided in JON server seem to be incorrect and/or missing.

Overall LDAP SSL support needs to be reevaluated and implemented in a clean/intuitive manner. There are two types of common SSL use-cases:

  1) SSL
  2) TLS

Seeing that LDAP SSL configuration prompts the user for the URL, 1) is accomplished using ldaps://. This makes the Use SSL check-box completely confusing and misleading. It appears that if I specify a protocol of ldap:// and also check the Use SSL check-box, my protocol specification is overridden with ldaps://. Although this might be desired, it is very confusing. Most commonly a "Use SSL" option is only provided when a host name is used (i.e. we aren't asking for a URL). So, we should ask for one or the other.

To support 2) we should be asking whether SSL is optional or required.

And in both cases, installation of certificates is not provided. Instead, one must install them in a JVM specified trust store or if using SSL sockets between agent and server, one must figure out where this is configured and how to get the public LDAP cert in the correct key file.

Comment 2 Mike Foley 2012-01-23 16:17:30 UTC
per scrum 1/23/2012 crouch, loleary, mfoley


Note You need to log in before you can comment on or make changes to this bug.