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:
ACI bind rule with ip keyword evaluates as DENY for IPv6 connections
Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-1.module+el8.1.0+3259+a5bc8ad3.x86_64
How reproducible:
always
Steps to Reproduce:
1. tests/suites/acl/keywords_test.py::test_user_can_access_the_data_when_connecting_from_any_machine_2
Actual results:
see attached errors log
Expected results:
ip=* should allow IPv6 addresses.
Additional info:
The problem here is that the code has no idea that ip="*" is a IPv4 or IPv6 wildcard. It would require a major change to the code to get this to work. Is there a valid use case for ip="*"? If not I'd like to close this as won't fix.
I can only think of denying a specific user to connect over network, but allowing over ldapi. But in this case the deny rule works. It's only 'allow IPv6 via ip=*' that fails.
Let's close it as WONTFIX. I will submit a PR to upstream to adjust the test so it won't affect package gating.
Thanks!