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.

Description of problem:

Chapter 11 of the Red Hat 7 System Administrators Guide misses a section (maybe 11.2) about the 389 Directory Server (http://directory.fedoraproject.org)

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

Red Hat Enterprise Linux 7.0 Beta System Administrators Guide, as of January 10th, 2014.

How reproducible:
Please check Red Hat Enterprise Linux 7.0 Beta System Administrators Guide, as published on Red Hat's site on January 10th, 2014.


Actual results:

There is no section about the 389 Directory Server (http://directory.fedoraproject.org)

Expected results:

A section about the 389 Directory Server should be available, since the 389 Directory Server is a more complete and enterprise-oriented LDAP solution than OpenLDAP.

Hello Răzvan

This topic is not something that has been requested before from those involved in maintaining the System Administrator's Guide, which is where LDAP is documented.

I will do some further research to see what the priority for this is. In the mean time please contact your support representative to ask their advice as to the best system to use for your application.

Thank you

Hello Razvan

The LDAP Directory Server for RHEL is called "Red Hat Directory Server".

Please see here for details:

http://www.redhat.com/en/technologies/cloud-computing/directory-server

This means this is not a subject for the System Admin Guide.

There is some documentation here:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/

Please contact your support representative if you require any more help with this request.

Thank you