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.
Description of problem:
As there are a lot of applications out there which have not an assigned port number in /etc/services it would make a lot of sense to add support for this in IPA.
It is currently possible to add this directly to the dirsrv by using ldapadd and a ldif file, this however is not very comfortable.
NSS services maps via sssd is a longer time
Version-Release number of selected component (if applicable):
3.0
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
neither the WebUI nor the CLI allows to add nss services
Expected results:
a command like:
ipa nss-services-add bogus --port=50000 --tcp=true --udp=true --description="A bogus service" --hosts=ipaclient.example.com --hostgroups=a-hostgroup
And the corresponding commands for modify and delete
Additional info:
At the moment this can be achived with an ldif file and ldapadd:
dn: cn=custom,cn=nisservices,dc=example,dc=com
changetype: add
cn: custom
cn: nisservices
objectclass: top
objectclass: nsContainer
dn: cn=example-srv,cn=custom,cn=nisservices,dc=example,dc=com
changetype: add
objectClass: ipService
objectClass: top
ipServicePort: 50010
ipServiceProtocol: tcp
ipServiceProtocol: udp
cn: example-srv
cn: totaly
cn: bogus
Adding ldap_service_search_base = cn=custom,cn=nisservices,dc=example,dc=com in the [domain/example.com] stanza in /etc/sssd/sssd.conf will do the job.
This will only solve if the services are unique allover the ipa clients. It would be great to attach different NSS services maps to different hosts and host groups.
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker long time ago (see link to the upstream ticket above), but it was unfortunately not given a priority neither in the upstream project, nor in Red Hat Enterprise Linux.
Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.
To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Trac ticket to expedite the solution.
There are a couple of use cases for services lookup. I.e. SAP. Each SAP instance has its own port where it listens and is bound to a specific host where the instance is running.
SAP wont start if the port is not matching the entry in /etc/services. Therefore it makes a lot of sense to manage the services centrally.
Thanks
Please see https://pagure.io/freeipa/issue/2638 and related comments. This is a big RFE that was deferred upstream. Until there is a very good business justification and collaboration with upstream on this RFE, the RFE does not have a high chances of being completed.