Hitachi ID Bravura Identity supports the notion of an "implementer-style" target system, where a human system administrator is asked to create, modify or delete a user object on the target system, in place of an automated Bravura Identity connector.
Implementer-style target systems are useful in two main circumstances:
- A custom or vertical-market target application has either a small or static population of users. The level of effort required to deploy automated integration to manage identities, entitlements or credentials (typically on the order of several days) is uneconomical.
- It is desirable to publish all applications in Bravura Identity, but there has not yet been time to integrate with all of them. Initially, changes on some applications will be handled manually, but over time more connectors will be deployed to expand automation.
Applications may also be configured in a hybrid mode, where some operations are automated using a connector but other operations are sent to human implementers to complete. For example, a CSV file might be used to enumerate users, groups and/or group memberships but a human implementer may be invited to complete changes manually.
Note that a full workflow to engage with system or application
administrator to complete tasks is built into Bravura Identity. Alternately,
integration with an external ticketing system can be used to
invite action on approved requests.
Sample Bravura Identity Request App Implementers View