Re: Uniqueness constraint over multiple attributes
On Thu, Jun 28, 2012 at 05:59:41PM +0200, Jan Beerden wrote:
On 06/20/2012 09:35 PM, Andrew Findlay wrote:
>The requirement for the primaryMail value to also appear as an
>aliasMail value could be enforced using the constraint overlay
>with the 'set' mechanism, something like: overlay constraint
>constraint_attribute primaryMail,aliasMail set "this/primaryMail &
>this/aliasMail"
>restrict="ldap:///o=myorg??sub?(objectClass=mailUser)" Andrew
This seamed to work at first but what this actually does is that it
forces a new aliasMail to already exist in it's own either
primaryMail or aliasMail.
Sorry - I don't understand that. Could you post some examples of what
works and what does not? It would be a good idea to include the slapd
configuration too.
Andrew
--
-----------------------------------------------------------------------
| From Andrew Findlay, Skills 1st Ltd |
| Consultant in large-scale systems, networks, and directory services |
| http://www.skills-1st.co.uk/ +44 1628 782565 |
-----------------------------------------------------------------------