As a follow-up, I figured out a workaround for the following error that
I reported earlier:

adding new entry "ou=auto.master,dc=example,dc=org"ldap_add: Invalid
syntax (21)     additional info: objectClass: value #1 invalid per

Original steps:
1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) Start slapd
3) Attempts to enter an automountMap entry causes an invalid syntax

1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) start slapd
3) stop and restart slapd again
4) Attempts to enter automountMap entry now succeed

Why this is necessary I can't say but the behavior is consistent.  This
extra restart was not necessary for versions of slapd+autofs that
shipped with 18.04 and previous Ubuntu versions.

Also I'm going to further show my ignorance here and say that I found
"caseExactMatch" in several other schema files too.  I'm wondering why
other users haven't run into something similar?
# find /etc/ldap/schema/ -type f -exec grep -q caseExactMatch {} \;
ap/schema/core.schema   <-- commented
/schema/core.ldif   <-- commented
Thank you again for your help on this.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.

  autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

Status in autofs package in Ubuntu:
Status in openldap package in Ubuntu:

Bug description:
  Ubuntu Release:
  # lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:      20.04

  Version of packages in use:
  # dpkg -l autofs autofs-ldap slapd | grep '^ii'
  ii  autofs         5.1.6-2ubuntu0.1       amd64        kernel-based 
automounter for Linux
  ii  autofs-ldap    5.1.6-2ubuntu0.1       amd64        LDAP map support for 
  ii  slapd          2.4.49+dfsg-2ubuntu1.3 amd64        OpenLDAP server (slapd)

  No errors from slaptest

  Actual Output:
  5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType 
inappropriate matching rule: "caseExactMatch"

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to