https://bugs.openldap.org/show_bug.cgi?id=10090
--- Comment #1 from Ondřej Kuzník <on...@mistotebe.net> --- On Mon, Aug 07, 2023 at 02:43:33PM +0000, openldap-...@openldap.org wrote: > Searching ACLs using regex expressions should allow for white space. > > olcAccess: to dn.subtree="dc=example,dc=com" by dn.regex="ou=Before\ > After,o=example[.]com,c=US$" read by * break > > or > > olcAccess: to dn.subtree="dc=example,dc=com" by dn.regex="ou=Before[ > ]After,o=example[.]com,c=US$" read by * break > > or any regex that contains a literal space results in a parse error. > > It seems like the string is broken on literal spaces irrespective of quoting. > > Debug output from slapd: > > 64cd845c.253aa590 0x7fe6f4fc9640 slapd: line 0: regular expression > "ou=Before\" > bad because of Trailing backslash > > This should also include other methods for expressing white space such as > `:space:` or `\w` pattern matches. > > olcAccess: to dn.subtree="dc=example,dc=com" by > dn.regex="ou=Before[[:space:]]After,o=example[.]com,c=US$" read by * break Can you provide a full example? I've tried to reproduce using the above and everything works just fine. And test006-acl also does the same and there haven't been any issues with that. Thanks, -- You are receiving this mail because: You are on the CC list for the issue.