- Overview
- About User Self-Service
- Self-Registration
- Social Registration
- OpenID Connect Authorization Code Flow
- Many Social Identity Providers, One Schema
- Setting Up Google as a Social Identity Provider
- Setting Up LinkedIn as a Social Identity Provider
- Setting Up Facebook as a Social Identity Provider
- Setting Up Amazon as an IDM Social Identity Provider
- Setting Up Microsoft as an IDM Social Identity Provider
- Set Up Apple as an IDM Social Identity Provider
- Setting Up WordPress as an IDM Social Identity Provider
- Setting Up WeChat as an IDM Social Identity Provider
- Setting Up Instagram as an IDM Social Identity Provider
- Setting Up Vkontakte as an IDM Social Identity Provider
- Setting Up Salesforce as an IDM Social Identity Provider
- Setting Up Yahoo as an IDM Social Identity Provider
- Setting Up Twitter as an IDM Social Identity Provider
- Setting Up a Custom Social Identity Provider
- Configuring the Social Providers Authentication Module
- Account Claiming: Links Between Accounts and Social Identity Providers
- Managing Social Identity Providers Over REST
- Testing Social Identity Providers
- Scenarios When Registering With a Social ID
- Social Identity Widgets
- 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
- Social Identity Provider Reference
- Google Social Identity Provider Configuration Details
- LinkedIn Social Identity Provider Configuration Details
- Facebook Social Identity Provider Configuration Details
- Amazon Social Identity Provider Configuration Details
- Microsoft Social Identity Provider Configuration Details
- WordPress Social Identity Provider Configuration Details
- WeChat Social Identity Provider Configuration Details
- Instagram Social Identity Provider Configuration Details
- Vkontakte Social Identity Provider Configuration Details
- Salesforce Social Identity Provider Configuration Details
- Yahoo Social Identity Provider Configuration Details
- Twitter Social Identity Provider Configuration Details
- Custom Social Identity Provider Configuration Details
- Social Identity Provider Button and Badge Properties
- 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.