RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
Embargoed:

Attachments (Terms of Use)


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.