How a Self-Registration Handler Works

A self-registration handler is similar to a typical logical attribute handler in the following ways:

You use the Logical Attribute API to write the custom handler. The custom handler extends the OrgSelectorAdapter abstract class, which extends LogicalAttributeAdapter.
You define an Organization Selector (self-registration handler) in the Management Console for your Identity Manager environment. The property definitions map the self-registration handler class file to one or more logical attribute names.
You add the logical attributes defined in the Management Console to your self-registration screen.
CA Identity Manager calls out to the self-registration handler when the user submits the self-registration screen containing the logical attributes.
The self-registration handler processes the information that CA Identity Manager passes to it (which includes the logical attribute values entered on the task screen), determines the organization where the user should be added, and passes the organization back to CA Identity Manager.

Three differences between typical logical attribute handlers and self-registration handlers are as follows:

The OrgSelectorAdapter class is only used with self-registration handlers.
CA Identity Manager calls out to the self-registration handler when the user changes tabs during self-registration. Logical attribute handlers are not invoked when tabs are changed.
Logical attributes are often associated with physical attributes. But a logical attribute mapped to a self-registration handler is typically not associated with a physical attribute.