The Vault API could extend the functionality of Vault to address specific workflow, action, etc. It's really powerful. But, unfortunately, those customization are client base. Then if the end-user remove or disable an add-in, you loose the control. Especially, when those add-in restrict transition between 2 states in a lifecycle (for medical company it's really problematic). My idea to address this: Solution A: define server-side add-in. But I think it's not so easy. All existing add-in must be rewritten. Not a good solution. Solution B: Check, on login if the add-in exist or not. To manage this, on user and group management, define the name of the required add-in and an option to define if only a warning must be displayed, if the login must be aborted or nothing (for debug purpose). Another option: Define if it's: on login, on change state, on ... each kind of event. Thanks in advance.
Show More