Our company is planning to onboard more applications into IDN. Some of the applications are hom grown applications and may not have direct connectors available to connect to these systems. In such case, how do we go about getting this system onboarded into IDN? Do we use JDBC connector in such cases? What is the general strategy to use for such cases?
Hi @Laks1 ,
The first strategy involves app prioritization and identifying available connectors.
If applications lack OOTB connectors, engage with app owners to understand the application’s architecture. For example, if the application uses a database backend, a JDBC connector can be used along with provisioning rules. If the application uses APIs, a Web Service connector is appropriate.
If neither option is supported, and the app team can export account and entitlement data to a CSV file, a Delimited/Flat File connector can be used. In this case, manual work items or ServiceNow tickets (if configured) will be generated, and provisioning and de-provisioning will be handled manually.
Hi @gourab ,
Thank you for the explanation. If the application is connected using Delimited flat file connector, and provisioning is done manually, what is the benefit of using a flat file connector?
It will help to add governance one the application like auto approval process , reporting who has access to what and also will help to manage the lifecycle of user and also you can perform periodic review .
Think like if you have to add governance and if you are not onboarding this application how you will add governance .