Description of problem:
Using luseradd to add new users to an ldap database creates them w/o the
Perhaps this is a user error as I know that I had initially created users that
did get into the database as inetOrgPerson. But this was under Fedora, so
perhaps this is a version issue (FWIW I looked into the RHEL source and
inetOrgPerson is already mentioned there)?
Even if a user error, if you could point me to the proper usage and this is
bugzilla'd and googlized it will help future libuser users :)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.luseradd <options> someuser
user is entered into ldap w/o objectclass inetOrgPerson
user should be inetOrgPerson
Ideally libuser would allow to even add further objectclasses like
inetLocalMailRecipient (expired mail routing draft) or other custom objectclasses.
Thanks for your report.
The "sn" (surname) attribute is mandatory in inetOrgPerson. Because luseradd
does not know and does not set the "sn" attribute, the created LDAP entry cannot
have the inetOrgPerson objectclass.
So, luseradd should allow specifying the gecos fields separately, with the side
effect that if one of them is present, "sn" must be present (because the
"account" objectclass does not contain the gecos fields), and inetOrgPerson is used.
Supporting other or custom object classes is outside of scope of libuser, which
is basically an alternative to (a subset of) NSS that allows modification of the
If you are a RHEL customer and have an active support entitlement, please
contact official Red Hat Support at https://www.redhat.com/apps/support/ to
allow correct prioritization of this issue.
I have developer licenses which come with no support options other than
bugzilla'ing issues, and I can't get any customer to channel this through him.
We can close it or wait for someone willing to invest his support options into
this bugzilla. I'll leave it up to you. Thanks!
Fixed in rawhide and F-12 libuser-0.56.13.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification. Issue is already fixed in RHEL-6/7.