freeipa team mailing list archive

[Andreas Hasenack <2034251@xxxxxxxxxxxxxxxxxx>]

Oops, this was fixed in bind9 already.

** No longer affects: bind9 (Ubuntu)

-- 
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bind-dyndb-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/2034251

Title:
  Incorrect rdn in the bind9 dn entry in the DEP8 test

Status in bind-dyndb-ldap package in Ubuntu:
  In Progress

Bug description:
  There is a small mistake in the bind9 DN entry, it should have an
  attribute matching the dn, but instead it  mentions a "replicator"
  entity that doesn't exist.

  It doesn't fail the test, but it's an incorrect LDAP entry and should
  be fixed:

  diff --git a/debian/tests/dyndb-ldap b/debian/tests/dyndb-ldap
  index 5482bc0..019bf24 100644
  --- a/debian/tests/dyndb-ldap
  +++ b/debian/tests/dyndb-ldap
  @@ -8,6 +8,7 @@ myhostname="dep8"
   ldap_admin_dn="cn=admin,${ldap_suffix}"
   ldap_admin_pw="secret"
   ldap_bind9_dn="uid=bind9,${ldap_suffix}"
  +ldap_bind9_rdn="uid: bind9" # match ldap_bind9_dn
   ldap_bind9_pw="secretagain"

   cleanup() {
  @@ -122,7 +123,7 @@ EOF
   create_bind9_uid() {
       ldapadd -x -D "${ldap_admin_dn}" -w "${ldap_admin_pw}" <<EOF
   dn: ${ldap_bind9_dn}
  -uid: replicator
  +${ldap_bind9_rdn}
   objectClass: simpleSecurityObject
   objectClass: account
   userPassword: {CRYPT}x

  This was fixed in debian already via https://salsa.debian.org/freeipa-
  team/bind-dyndb-ldap/-/commit/6b5096776ee0502d9cac3966b6aa5f4da4cef664

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind-dyndb-ldap/+bug/2034251/+subscriptions