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/2801
In time we have had requests to create system accounts so that some legacy services can bind to the directory with a simple username/password to perform some operations. For example password sync services from an out of Realm machine.
There are 2 types of system accounts we want to cover:
* POSIX system accounts, with UID and GID. This can cover shared accounts for services that is used on different machines and thus cannot use standard services. In future, we should be able to '''request certificates''' for these accounts.
* Simple, non-POSIX system accounts only for LDAP only operations (`simpleSecurityObject`).
Password policy should not apply for either of them.
Hello,
This seems to be a valid RFE but not with a high priority.
There is a workaround to use user accounts instead.
This bug will be closed as DEFERRED. Upstream ticket at this time will continue to be open.
Thanks
Dmitri