[Date Prev][Date Next]
Re: set-based constraint for prefix
- To: <firstname.lastname@example.org>
- Subject: Re: set-based constraint for prefix
- From: Raphaël Ouazana-Sustowski <email@example.com>
- Date: Tue, 04 Feb 2014 11:48:45 -0000
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com>
- User-agent: Roundcube Webmail/0.8.5
Le 03/02/2014 19:26, Michael Ströder a écrit :
Maybe I'm overlooking something obvious...
I'd like to enforce a prefix naming convention by using a set-based
The idea is that 'cn' value of an entry should *start* with the 'cn'
the superior entry and a hyphen.
Example with Superior entry has 'cn: example':
example-foo -> accept
examplefoo -> disallow
foo-bar -> disallow
My problem is the "start with" since I cannot find a way to express
wildcard string in a set.
I think the wildcard can be expressed in a filter. Some something like
this should work (untested):
this & ( [ldap:///] + this/entryDn + [??base?(cn=] + this/-1/cn + [-*)]