- 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 Completion and Metadata
Progressive profile completion requires that you track object metadata. Configure tracking of the following data:
createDate: The date the user was created; used in theonCreateUser.jsscript in theopenidm/bin/defaults/scriptdirectory.loginCount: The number of logins, by user.stagesCompleted: Used to track progressive profile forms, and whether they've been completed, by user.
User acceptance of Terms & Conditions is tracked by default (see "Terms & Conditions").
Defining Overall Profile Completion
A user profile is based on every item in managed.json where both viewable and userEditable are set to true. Every qualifying item has equal weight.
So, if there are 20 qualifying items in managed.json, a user who has entries for 10 items has a Profile completion percentage of 50.