This guide explains how to map fields passed by your SSO provider to Bettermode member fields when implementing a Custom SSO setup.
Compatibility Requirements
This mapping applies only if your OAuth2 provider follows OpenID Connect standards and returns user information including the user ID, email, and name.
Field Mapping Order
Bettermode maps JSON fields to member profile fields using the following priority order for each field:
- externalId:
id,ID,userId - email:
email,user_email - name:
name,display_name,displayName,full_name,pseudo - username:
username,user_login,nickname - profilePicture:
picture,icon_url - fields:
fields
Bettermode checks each field name in order and uses the first match it finds.
Nested Data Objects
If a field is not found at the root level of your JSON response, Bettermode looks for it nested under a data key. This applies to all fields listed above.
Standard Compatibility
This mapping covers most standard user information endpoints, including WP OAuth Server.