- Overview
- About User Self-Service
- Self-Registration
- Social Registration
- OpenID Connect Authorization Code Flow
- Many Social Identity Providers, One Schema
- Amazon Social Identity Provider
- Apple Social Identity Provider
- Facebook Social Identity Provider
- Google Social Identity Provider
- Instagram Social Identity Provider
- LinkedIn Social Identity Provider
- Microsoft Social Identity Provider
- Salesforce Social Identity Provider
- Twitter Social Identity Provider
- Setting Up Vkontakte as an IDM Social Identity Provider
- WeChat Social Identity Provider
- WordPress Social Identity Provider
- Yahoo Social Identity Provider
- Custom Social Identity Provider
- Configure the Social Providers Authentication Module
- Account Claiming: Links Between Accounts and Social Identity Providers
- Manage Social Identity Providers Over REST
- Test Social Identity Providers
- Scenarios When Registering With a Social ID
- Social Identity Widgets
- Social Identity Provider Button and Badge Properties
- Progressive Profile
- Password Reset
- Username Retrieval
- Additional Configuration
- Configure Notification Emails
- Configure Privacy and Consent
- Configure UMA, Trusted Devices, and Privacy
- Terms & Conditions
- Tokens and User Self-Service
- End User UI Notifications
- Configure Google reCAPTCHA
- Configure Identity Fields
- Configure Security Questions
- Add Custom Policies for Self-Registration and Password Reset
- Self-Service End User UI
- Custom Self-Service Stages
- Self-Service Stage Reference
- All-In-One Registration
- OpenAM Auto-Login Stage
- Attribute Collection Stage
- Captcha Stage
- Conditional User Stage
- Consent Stage
- Email Validation Stage
- IDM User Details Stage
- KBA Security Answer Definition Stage
- KBA Security Answer Verification Stage
- KBA Update Stage
- Local Auto-Login Stage
- Parameters Stage
- Patch Object Stage
- Password Reset Stage
- Self-Registration Stage
- Social User Claim Stage
- Terms and Conditions Stage
- User Query Stage
- IDM Glossary
Progressive Profile
Progressive profile completion lets you gather profile attributes asynchronously to enrich your users' profile data, and enhance engagement with your customer base. Profile completion requires the creation of one or more forms to collect user data.
IDM implements progressive profile completion as a default self-service process. You can use this process as an example of how to build additional functionality into a custom client application, using the Self-Service REST API.
After activating Self-Registration, users need only the following information to register:
User name
First name
Last name
Email address
Progressive profile completion lets you collect additional information, limited by the attributes defined in the managed.json
file for your project.
In the following sections, you'll examine how you use progressive profile completion to ask or require more information from users. You're limited only by what properties are defined in your project's managed.json
file.