Besides registration, you may enable self-service profile management and specify which local identity fields users can update on the profile management page.
To illustrate the configuration steps, consider the sample use case in Setting up self-service registration or Enabling third-party identity providers with the added requirement of allowing users to modify their mobile number and to remove their local accounts.
Configuration steps:
As the required components remain the same, the step sequence matches those in Setting up self-service registration and Enabling third-party identity providers as well. If you require more information for a given step, refer to the same step in one of the aforementioned pages.
- Set up PingDirectory to connect with PingFederate.
- Create an authentication policy contract.
-
Configure profile management when creating a new or reconfiguring an existing
local identity profile using the
configuration wizard.
- Configure an HTML Form Adapter instance for customer identities.
- Create an IdP authentication policy.
-
Provide the profile management URL to users.
- Go to the screen.
- Select the local identity profile that you have configured profile management in step 3.
- Copy the profile management URL as shown on the Summary screen and pass it to the users.
You have now successfully enabled profile management. Authenticated users can review and modify the local identity fields that have been configured to be shown on the profile management page and delete their local accounts if the option to do so has been enabled.
The following screen capture provides a sample of the profile management page based on the sample use case:
Suppose you have added Facebook, Google, LinkedIn, and Twitter to the local identity profile. When a user accesses the profile management page, the user will see a page similar to the following screen capture:
If you have only one authentication source, the profile management page reminds the users that they must set a password for their local accounts before disconnecting the third-party identity provider.