Is there a "Property Value must be Unique" policy rule in a Property Generation and Validation ( PGV) policy?
An Enhancement Request has been created to integrate this functionality into Active Roles. This Enhancement Request can be tracked using Enhancement ID 277133.
Product Management will evaluate the request and this feature may become available in a future release of the product.
There are no guarantees that this specific enhancement request will be implemented in a future release. For more information regarding our Enhancement Request policy, refer to our Global Support Guide on the Support Portal.
Out of the box there is no "Property Value must be Unique" policy rule in a Property Generation and Validation policy, however, as a workaround, it is possible to enforce uniqueness on the samAccountName and build other attributes containing this unique value.
Then add a Property Generation and Validation policy for the attribute where a uniquness constraint is desired, with a rule based on samAccountName.
The only other option would be to develop a custom scripted solution. For more information on this option, please consult Professional Services or Sales.