Previous Topic: Support for Binary-type AttributesNext Topic: How to Enable Support for Mapping of Non-mandatory Fields in Provisioning Manager


Support for Mandatory Attributes on a JDBC Endpoint

To support attributes that the JDBC endpoint defines as mandatory (that is, NOT NULL), but do not need to be mandatory from the provisioning point of view, the JDBC connector allows you to use an empty value for the provisioning attribute.

When you create an account and are mapping a mandatory attribute on the endpoint to a provisioning attribute that is non-mandatory, for example, a description field, and you do not enter a value for the description field, the JDBC connector maps the empty provisioning attribute to the endpoint attribute by populating the NOT NULL column on the endpoint database with spaces.

To support mapping of non-mandatory fields in Provisioning Manager, CA IAM CS contains a NullValueClassConverter that converts empty values in non-mandatory provisioning attributes to spaces in mandatory attributes on the endpoint.

For example, empty values can occur on a legacy database system has a description field that is NOT NULL on the table being mapped to a user account. However, the description field is not set to mandatory in the Provisioning Manager, which means you do not have to enter a description for a user to create an account. The NullValueClassConverter is used to store the empty value.

The property nullValue in the pluginConfig class in the NullValueClassConverter is set to a space by default. You can change nullvalue to other values, but changing nullvalue requires additional configuration of the endpoint database.

For JDBC endpoints, CA IAM CS loads the converter automatically. For other types of endpoints, for example, JNDI, manually configure CA IAM CS to load the converter.