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:
Per summary. This may be a reasonable behaviour for POSIX groups, but should not be blocked for non-POSIX groups.
Version-Release number of selected component (if applicable):
ipa-server-4.2.0-15.el7_2.17.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Navigate to User Groups, + ADD
2. Provide reasonable group name, e.g. "équipe"
3. See error message
4. Switch to Normal or Extended group, same message
Actual results:
Error message
Expected results:
Takes reasonable group name
Additional info:
ldapadd can add a group with such a name just fine. The UI seems to display and operate on the groups OK.
If IPA displays groups from external sources, it will see groups with UTF characters.
LDAP spec allows for UTF characters in group names.
Suspect check was implemented for POSIX groups and was not limited to only POSIX groups.
Currently all group types shares the same validation logic for their name.
It is true that it for non-posix groups doesn't have to be so strict. But this change may bring other issues. E.g. it may prevent non-posix to posix group conversion. Or other currently unforseen one.
Given that IPA upstream has ~ 1200 opened bugs and RFEs we need to prioritize carefully.
So far this RFE doesn't seems to have big enough demand to be implemented/investigated more.
There weren't any other request for this RFE. Given the possible limitation of other use cases (change to POSIX), the change is controversial. Thus closing.