Bug 2252789
| Summary: | Unable to add "person" objectClass to user in RHDS console of cockpit browser. | ||
|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | thierry bordaz <tbordaz> |
| Component: | cockpit-389-ds | Assignee: | LDAP Maintainers <idm-ds-dev-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | LDAP QA Team <idm-ds-qe-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 11.7 | CC: | idm-ds-dev-bugs, spichugi |
| Target Milestone: | DS12.5 | Keywords: | Triaged |
| Target Release: | dirsrv-12.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-26 13:50:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Okay, currently, there are three user types that can be created. Basic Account - This type of user entry uses a common set of objectclasses (nsPerson, nsAccount, and nsOrgPerson). Posix Account - This type of user entry uses a similar set of objectclasses as the Basic Account (nsPerson, nsAccount, nsOrgPerson, and posixAccount), but it includes POSIX attributes like:uidNumber, gidNumber, homeDirectory, loginShell, and gecos. Service Account - This type of entry uses a bare minimum of objectclasses (nsAccount, and applicationProcess) and attributes to create a simple object used to represent a service (not a user identity). They use predefined objectClasses that are not modifiable during the creation. After the user is created, it's possible to modify it as a generic LDAP Entry, and you can add "person", "inetOrgPerson" or any other objectClass that you need (I just checked it on Fedora Rawhide and it works) So the issue is not that it's impossible to add "person" objectClass to user in RHDS console of cockpit browser. It's possible, but only after creation. The question is - if we want to add limited objectClass functionality to the user creation... But it'll be an RFE, I think. This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-73. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: Unable to add "person" objectClass to user in RHDS console of cockpit browser. Pre-Requisites : The LDAP schema is RFC4519 compliant. • All users have an objectClass of inetOrgPerson. • All groups have an objectClass of groupOfUniqueNames. • All groups have a group membership attribute of uniqueMember. • All users and group objects have entryUUID configured (The objects have a unique GUID and should not be changing) Version-Release number of selected component (if applicable): RHDS11 How reproducible: In order to add the inetOrgPerson objectClass to the user, we need the person objectClass. (sn attribute is mandatory for inetOrgPerson and is accessible with person objectClass.) While adding user, it prints that it will be inetOrgPerson objectClass but when you click next, the 3 user type options don't have this class. The sn attribute isn't proposed or listed there (since it need person objectClass as expected). After adding the user without objectClass "person", trying to edit it to add that objectClass but still the same issue persists. Expected results: Should have an option to add objectClass "person" while adding the user.