I'd like the ability to be able to package the Identity Vault schema so that I can move it between environments.

The package should be an Identity Vault package.

I'd like the ability to package individual classes and their associated attributes, or to select multiple classes.

This should only make changes to the Designer copy of the schema - it remains the operator’s responsibility to manage the deployment of changes into eDirectory.

When the package is added to the Identity Vault object, the schema extensions should be added.

When the package is removed from the Identity Vault object, the schema extensions should be removed.

Comments

  • Hard to guarantee removal of schema extensions if they are still in use. It should flag this and refuse to remove package until all objects are cleared of relevant schema in eDir.

  • @Alex M - that's why I suggested the package should only modify the designer copy of the schema. It would then be down to the admin to make sure that eDirectory is in a state where the schema changes are deploy-able. I don't see a safe way of automating the changes directly into eDirectory.