Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/1957
The NIS server plugin for the directory server can either bind to an available port selected at runtime by using bindresvport(), or to a specific port. Either way, it'll notify the portmapper of which one it's using, so clients will be able to find it. For firewalling purposes, though, an admin is likely to want to know which port it will use ahead of time. A port is specified by setting "nsslapd-pluginarg0" to the desired port number (the plugin's documentation uses "541" as an example, but any port below 1024 should do as well) in the entry which instructs the server to load the plugin.
Ideally, I think the tool which enables and disables the plugin should be able to set and unset this parameter. Failing that, I guess we probably want to set one by default so that the server installation script can advise the administrator to punch a hole in the firewall for NIS, as it already does for Kerberos and LDAP services.
Converted to a documentation bug instead.
To set a specific port you'll need to modify the plugin configuration entry in LDAP and add the nsslapd-pluginarg0 with the value of the port you want to listen on.
An example to set port 514 is:
# ldapmodify -x -D 'cn=directory manager' -W Enter LDAP Password: dn: cn=NIS Server,cn=plugins,cn=config changetype: modify add: nsslapd-pluginarg0 nsslapd-pluginarg0: 514
modifying entry "cn=NIS Server,cn=plugins,cn=config"
# /sbin/service dirsrv restart