ngpb5 (ngpb5) asked a question.
Custom API User Provisioning Connectors
Hi All, we are researching options for building custom user provisioning connectors to Okta Identity Governance (OIG). Our company works in the banking industry and we hope are working to streamline automation of life cycle management with Okta.
We'd be interested in learning more about what custom connectors other major banks or financial services companies have built to provision users. Specifically things like:
- What applications have you integrated leveraging APIs for automatic user lifecycle management?
- What tips do you have for scoping and planning a custom connector build?
- What lessons learned or pitfalls to avoid can you share?
Not specific to the banking industry. and I suspect most banking industry customers would not provide the information of the services they connect to. However, the approach for custom connector are common.
Consider all of your user journeys. Not just provisioning. What other states and data to you need to consider.
Consider the sunny day journeys, but make sure you think through the broken journeys. These are the ones that will trip you up and leave users in an expected state, or worse with unexpected access
Apply good engineering principles around testing. This is code, not matter how you apply the business logic.
Try to make the connections self healing. Those APIs are not 100% uptime. You will see failures.
If you can self heal, alert. If something breaks make sure someone knows about it.