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.
Bug 679460 - [RFE] Interpret IPV6 addresses for ACIs, replication, and chaining
Summary: [RFE] Interpret IPV6 addresses for ACIs, replication, and chaining
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: alpha
: 7.0
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 512820 690319
TreeView+ depends on / blocked
 
Reported: 2011-02-22 15:57 UTC by kent lamb
Modified: 2020-09-13 19:59 UTC (History)
8 users (show)

Fixed In Version: 389-ds-base-1.3.1.2-1.el7
Doc Type: Enhancement
Doc Text:
Cause: Lack of full support of IPv6 addresses in features such as replication, access control, and chaining. Consequence: Some of the main features of the server can be used in IPv6 environments. Change: Added IPv6 support to all the server plugins Result: Directory Server can now fully handle IPv6 addresses.
Clone Of:
Environment:
Last Closed: 2014-06-13 10:01:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 196 0 None None None 2020-09-13 19:59:22 UTC

Comment 2 Rich Megginson 2012-01-09 17:43:06 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/196
Comment 4 mreynolds 2012-05-11 18:32:44 UTC 
This fix has been checked into the main trunk.

To verify fix:


Replication: 

   manually create an agreement and set the nsDS5ReplicaHost with the IPv6  address, and make sure you can replicate entries


Chaining:

   use an IPv6 address for nsfarmserverurl.  


Note:  For LDAP urls, the IPv6 Address must be in brackets:

ldap://[fe80::250:45ff:fe02:7fe8]:389


Access Control:

   Example of aci that uses IPv6:

aci: (target ="ldap:///dc=example,dc=com")(targetattr !=
 "userPassword")(version 3.0;acl "Anonymous IPv6 read-search access";
 allow (read, search, compare)(userdn = "ldap:///anyone") and (ip="2000:db8:0:f101::12");)
Comment 6 mreynolds 2012-10-09 19:22:47 UTC 
This fix will be rhel 6.4(DS 9), and in 389-ds-base-1.3.0.a1.
Comment 9 Rich Megginson 2013-10-01 23:24:52 UTC 
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.
Comment 11 Amita Sharma 2013-11-12 09:16:51 UTC 
Successfully Added ACI using IPv6 address::
[root@dhcp201-149 ~]# ldapmodify -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 << EOF
> dn: dc=example,dc=com
> changetype: modify
> replace: aci
> aci: (target ="ldap:///dc=example,dc=com")(targetattr !="userPassword")(version 3.0;acl "Anonymous IPv6 read-search access";allow (read, search, compare)(userdn = "ldap:///anyone") and (ip="2000:db8:0:f101::12");)
> EOF
modifying entry "dc=example,dc=com"
Comment 12 Ján Rusnačko 2013-11-12 12:12:03 UTC 
Successfully tested replication:
[root@localhost admin-serv]# ldapsearch -D "cn=directory manager" -w Secret123 -b "cn=test,cn=replica,cn=ou\3Dtest\2Cdc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" -LLL
dn: cn=test,cn=replica,cn=ou\3Dtest\2Cdc\3Dexample\2Cdc\3Dcom,cn=mapping tree,
 cn=config
objectClass: top
objectClass: nsDS5ReplicationAgreement
description: test
cn: test
nsDS5ReplicaRoot: ou=test,dc=example,dc=com
nsDS5ReplicaHost: [::1]
nsDS5ReplicaPort: 1389
nsDS5ReplicaBindDN: uid=replmgr,dc=example,dc=com
nsDS5ReplicaTransportInfo: LDAP
nsDS5ReplicaBindMethod: SIMPLE
nsDS5ReplicaCredentials: {DES}3iMsHyML5/QgiI3nMoqaYw==
nsds5replicareapactive: 0
nsds5replicaLastUpdateStart: 20131112120823Z
nsds5replicaLastUpdateEnd: 20131112120826Z
nsds5replicaChangesSentSinceStartup:: MToxLzAg
nsds5replicaLastUpdateStatus: 0 Replica acquired successfully: Incremental upd
 ate succeeded
nsds5replicaUpdateInProgress: FALSE
nsds5replicaLastInitStart: 20131112120728Z
nsds5replicaLastInitEnd: 20131112120730Z
nsds5replicaLastInitStatus: 0 Total update succeeded

Feature is implemented in latest RHEL7 389, testing is yet to be done - bugs in this feature will be filed separately.
Comment 13 Sankar Ramalingam 2013-11-12 13:54:48 UTC 
Configured replication with IPv6 address and encountering "function not implemented" errors.

==> /var/log/dirsrv/slapd-M2/errors <==
[12/Nov/2013:08:52:00 -0500] slapi_ldap_bind - Error: could not send bind request for id [cn=SyncManager,cn=config] authentication mechanism [SIMPLE]: error -1 (Can't contact LDAP server), system error -5992 (function not implemented.), network error 115 (Operation now in progress, host "[2620")

==> /var/log/dirsrv/slapd-M1/errors <==
[12/Nov/2013:08:52:00 -0500] slapi_ldap_bind - Error: could not send bind request for id [cn=SyncManager,cn=config] authentication mechanism [SIMPLE]: error -1 (Can't contact LDAP server), system error -5992 (function not implemented.), network error 115 (Operation now in progress, host "[2620")
Comment 14 Sankar Ramalingam 2013-11-12 14:00:46 UTC 
(In reply to Sankar Ramalingam from comment #13)
> Configured replication with IPv6 address and encountering "function not
> implemented" errors.
> 
> ==> /var/log/dirsrv/slapd-M2/errors <==
> [12/Nov/2013:08:52:00 -0500] slapi_ldap_bind - Error: could not send bind
> request for id [cn=SyncManager,cn=config] authentication mechanism [SIMPLE]:
> error -1 (Can't contact LDAP server), system error -5992 (function not
> implemented.), network error 115 (Operation now in progress, host "[2620")
> 
> ==> /var/log/dirsrv/slapd-M1/errors <==
> [12/Nov/2013:08:52:00 -0500] slapi_ldap_bind - Error: could not send bind
> request for id [cn=SyncManager,cn=config] authentication mechanism [SIMPLE]:
> error -1 (Can't contact LDAP server), system error -5992 (function not
> implemented.), network error 115 (Operation now in progress, host "[2620")

Looks like the replication fails for SSL configured instances, not for non-ssl.

[root@ibm-x3650m4-01-vm-14 MMR_WINSYNC]# /usr/bin/ldapsearch -x -h 2620:52:0:102f:5054:1ff:fe3c:e136 -p 1289 -D "cn=Directory Manager" -w Secret123 -b "cn=replica,cn=\"dc=passsync,dc=com\",cn=mapping tree,cn=config" nsds5replicaLastUpdateStatus nsDS5ReplicaTransportInfo
# extended LDIF
#
# LDAPv3
# base <cn=replica,cn="dc=passsync,dc=com",cn=mapping tree,cn=config> with scope subtree
# filter: (objectclass=*)
# requesting: nsds5replicaLastUpdateStatus nsDS5ReplicaTransportInfo 
#

# replica, dc\3Dpasssync\2Cdc\3Dcom, mapping tree, config
dn: cn=replica,cn=dc\3Dpasssync\2Cdc\3Dcom,cn=mapping tree,cn=config

# 1289_to_1389_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com, replica, dc\3D
 passsync\2Cdc\3Dcom, mapping tree, config
dn: cn=1289_to_1389_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com,cn=replica,
 cn=dc\3Dpasssync\2Cdc\3Dcom,cn=mapping tree,cn=config
nsds5replicaLastUpdateStatus: 0 No replication sessions started since server s
 tartup
nsDS5ReplicaTransportInfo: LDAP

# 1289_to_1489_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com, replica, dc\3D
 passsync\2Cdc\3Dcom, mapping tree, config
dn: cn=1289_to_1489_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com,cn=replica,
 cn=dc\3Dpasssync\2Cdc\3Dcom,cn=mapping tree,cn=config
nsds5replicaLastUpdateStatus: 0 No replication sessions started since server s
 tartup
nsDS5ReplicaTransportInfo: LDAP

# 1289_to_1616_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com, replica, dc\3D
 passsync\2Cdc\3Dcom, mapping tree, config
dn: cn=1289_to_1616_on_ibm-x3650m4-01-vm-14.lab.eng.bos.redhat.com,cn=replica,
 cn=dc\3Dpasssync\2Cdc\3Dcom,cn=mapping tree,cn=config
nsds5replicaLastUpdateStatus: -1 Unable to acquire replicaLDAP error: Can't co
 ntact LDAP server
nsDS5ReplicaTransportInfo: SSL
Comment 15 Rich Megginson 2013-11-12 14:31:33 UTC 
SSL requires a hostname, not an IPv4/IPv6 address.  This is for the hostname checking for the cn in the server cert subject DN.

What you have to do, in this case, is ensure that the hostname resolves to an IPv6 address.
Comment 16 Ján Rusnačko 2013-11-12 14:52:00 UTC 
Since the feature is implemented and the hostname issue is addressed by comment #15, marking as VERIFIED. Testplan for this feature is pending and new bugs will be filed separately.
Comment 17 Zailo Leite 2014-01-30 17:12:35 UTC 
FWIW, ACIs with ip addresses on multihomed servers are still broken in 1.3.1.6-10
Comment 18 Noriko Hosoi 2014-01-30 17:29:05 UTC 
(In reply to Zailo Leite from comment #17)
> FWIW, ACIs with ip addresses on multihomed servers are still broken in
> 1.3.1.6-10
Hi Zailo,
Could you please open a ticket (if not yet) at https://fedorahosted.org/389/newticket with the sample ACIs and the broken results?
Thanks!
--noriko
Comment 19 Zailo Leite 2014-02-26 16:29:35 UTC 
Looks OK in 1.3.2.9-1 . Thanks!

Z
Comment 20 Ludek Smid 2014-06-13 10:01:42 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.