Chapter 2: Example Basic Custom Connector

We have endpoint is a flat file. Our file keeps records of users in format account id|encode password|city|telephone number.

Figure 2-3 shows our custom connector and endpoint

We will develop the custom connector supports add, delete, modify and search the accounts in the file as endpoint. To understand better, we skip role or group features.

Before development, you have to define required attributes for endpoint, account and policy (or account template) class. Endpoint class requires file path for saving users information. We define username and password for connecting endpoint but we do not use in this example but you can refer these attributes in future. 

Figure 2-4 shows attributes of endpoint, policy and account class.

                Policy or account template requires attributes for provisioning’s attribute mapping. Account class requires id, password, city, and telephone number.