Connectors play a very important role in any IDM deployment as it determines the scope of the endpoints that can be successfully integrated with the IDM infrastructure. The list of supported connector endpoint types is a crucial factor for making a purchase decision or for identifying a long term roadmap for any IDM project. IDM implementation is a big-ticket, multi-year purchase for any organization and support for a particular endpoint can make or break a deal.
There are primarily two options for customers if a particular endpoint is not supported. Either, they contact CA to provide a custom connector (with support from GD) or they check in-house if they can develop a custom connector. The second option is quite prevalent at those customers where they have big stakes in their existing IDM implementations.
Our IDM deployment includes a connector SDK that helps in writing a custom connector using industry standard skillsets (Java, JNDI, LDAP, XML, Spring framework). The learning curve for developing the custom connector is steep as there is not enough documentation available on CA site (or it’s outdated) for setting up a developer’s workbench.
Our aim is to remove blocks for our customers, and if they wish to develop their own custom connector, let them do it. If we want our customers to be successful, we need to support a step-by-step setup for developer’s workbench for developing a custom connector using CA SDK. It would help in getting the DEV environment of the customer up and running in a very short time enabling success for the customer.
In addition, we should publish a list of all custom connectors that were developed in the past and include it in the product support sheet with a tag-‘Additional work required’. We may need to provide the source code too if we want our developer’s community to thrive. It would provide a great reference to any developer to churn out custom connectors quickly as per their requirements.
The above steps would ensure an ongoing adoption of our IDM system, with lots of acceptance in the developer’s communities.
My idea is to –
- Support a step-by-step setup for developer’s workbench for developing a custom connector using CA SDK (for industry standard IDEs like eclipse)
- Publish a list of all custom connectors that were developed in the past and include it in the product support sheet, along with their source code published on CA site.