Bug 687939 - RFE: add ability to have SSL configured for TLS but not a separate SSL listener
Summary: RFE: add ability to have SSL configured for TLS but not a separate SSL listener
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: 7.3
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 690319
TreeView+ depends on / blocked
 
Reported: 2011-03-15 18:52 UTC by Rob Crittenden
Modified: 2020-09-13 19:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 01:54:06 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 61 0 None None None 2020-09-13 19:48:59 UTC

Description Rob Crittenden 2011-03-15 18:52:34 UTC 
Description of problem:

Currently in order to enable TLS on the unsecure port you need to define a second secure port, 0 is not allowed. It would be nice to be able to have just the single listener.

Version-Release number of selected component (if applicable):

389-ds-base-1.2.8-0.2.a2.fc14.x86_64
Comment 1 Martin Kosek 2012-01-04 13:27:48 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/61
Comment 6 wibrown@redhat.com 2018-03-15 01:54:06 UTC 
Hi,

Closing this as won't fix. I'm about to make a submission to the IETF deprecating StartTLS in LDAP in favour of LDAPS. I have already gained support from some OpenLDAP community members.

Once the draft is done, this makes this request obsolete. 

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