Score:0

Unique overlay: unique value within each (dynamic) branch possible?

mx flag

The relevant part of the directory is structured like this (sample dn)

integrationId=my-uuid,ou=integrations,accountId=my-account-uuid,ou=accounts,ou=...

integrationId and accountId are custom schema attributes, used with custom objectClasses. We have accounts for each customers, and within each account, we want to have integrations, that have an attribute (cn in this case) with unique values within the account.

Is there a way to express this with the unique overlay, with a combination of unique_uri and filter?

Can an ldap uri contain any kind of wildcard or placeholder, to effectively create a unique constraint for each existing accountId?

From the Unique Overlay Manpage, I can not really tell how to do this. Is this indeed not possible (in which case we would implement the constraint in application code)?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.