Programming Guides › Connector Programming Guide › Connector Concepts › Scope

Scope

When designing a connector you consider the following:

• How many object classes your connector must support.

  We recommend that you use the built-in DYN parser table support bundled with the CA IdentityMinder Provisioning Server. Using the built-in DYN parser table support greatly simplifies the connector development process. That is, you do not have to understand parser tables and you get a basic Provisioning Manager user interface for free. However for this release, if you require more than a single account, group and container object classes, then define your own custom parser tables.

  Note: For more information see, the C++ Provisioning Server SDK Guide.

  An important distinction here is between objects that are fully managed versus objects that exist solely so that managed objects can reference them. For example, there can be a requirement to display a list of all native roles so that the customer can choose which apply to a newly created account, even though the native roles are not managed.

• What are the minimum attributes you require to implement on each object class to provide a useful shallow connector?

  We recommend that you address this requirement in your initial phase one delivery, and then build on this functioning base, rather than attempt to implement a deep connector immediately.