1. On the PingFederate administrative console, go to Authentication > Policies > Policies.
  2. Select the IdP Authentication Policies check box.
  3. Open the authentication policy that you created in your initial registration configuration.
  4. In the Policy area, define a policy path for user registration.
    1. Under the HTML Form Adapter instance, click Rules.
    2. On the Rules dialog, from the Attribute Name list, select policy.action.
    3. From the Condition list, select equal to.
    4. In the Value field, enter identity.registration.
    5. In the Result field, enter a name, such as Registration. This appears as a new policy path that branches from the PingOne Verify IdP Adapter.
    6. Click Done.
  5. After the HTML Form Adapter instance, for the Fail path, select Done.
  6. After the HTML Form Adapter instance, for the Registration path, select the local identity profile that you created for PingOne Verify.
    1. Click Local Identity Mapping.
    2. On the Inbound Mapping tab, map the registration form fields to the input policy contract attributes.
      Example mappings
      Inbound Mapping Fulfillment Value
      firstName regFirstName
      email registrar@example.com
    3. On the Contract Fulfillment tab, map values for the outbound contract.
      Example mappings
      Outbound Mapping Fulfillment Source Value
      attr1 Local Identity (Verify Identity Profile) email
      subject Local Identity (Verify Identity Profile) firstName
    4. Click Done.
  7. After the HTML Form Adapter instance, for the Success path, configure the standard (non-registration) authentication path.
  8. Click Done.
  9. In the Policies window, click Save.