메인 콘텐츠로 건너뛰기

User Mapping

When users sign in through OAuth providers, Casdoor automatically captures their basic profile information like username, email, and avatar. However, identity providers often return additional claims in their OAuth responses that contain valuable user data. The User Mapping feature allows you to map these extra claims to specific user profile fields in Casdoor.

Supported Fields​

You can map OAuth provider claims to the following user fields:

  • phone - Phone number
  • countryCode - Country calling code
  • firstName - First name
  • lastName - Last name
  • region - Geographic region
  • location - Full location or address
  • affiliation - Organization or company affiliation
  • title - Job title or position
  • homepage - Personal website URL
  • bio - Biography or description
  • tag - Custom tag or category
  • language - Preferred language
  • gender - Gender identity
  • birthday - Date of birth
  • education - Educational background
  • idCard - ID card number
  • idCardType - Type of ID card

Standard fields (id, username, displayName, email, avatarUrl) are handled automatically and don't need mapping configuration.

Configuration​

To configure user mapping for an OAuth provider:

  1. Navigate to Providers in the top menu
  2. Select or create an OAuth provider (e.g., Okta, Azure AD B2C, Google)
  3. Scroll to the User mapping section
  4. Add mappings by specifying:
    • User field: The Casdoor user field you want to populate
    • Claim name: The exact claim name from your OAuth provider's response

For example, if your identity provider returns a claim named given_name and you want to map it to the user's first name in Casdoor:

  • User field: firstName
  • Claim name: given_name

Provider-Specific Examples​

Okta​

Okta returns claims like given_name, family_name, and locale. You might configure:

  • firstName → given_name
  • lastName → family_name
  • language → locale

Azure AD B2C​

Azure AD B2C can return custom claims configured in your user flows. For instance:

  • phone → extension_PhoneNumber
  • title → jobTitle
  • location → city

Generic OAuth Providers​

Most OAuth providers following standard protocols return claims in their userinfo endpoint. Check your provider's documentation to find available claim names.

Behavior​

The mapping works with these characteristics:

  • Non-destructive: Existing user field values are preserved. Mapping only updates empty fields.
  • Automatic sync: When users sign in via OAuth, the mapping is applied automatically.
  • Flexible: Each provider can have its own unique mapping configuration.
  • Extra claims: All claims from the provider are stored in the user's extra data, even if not explicitly mapped.

Common Scenarios​

Enterprise SSO​

When integrating with enterprise identity providers like Okta or Azure AD, you often want to sync organizational data:

title → jobTitle
affiliation → companyName
region → officeLocation

Social Login Enhancement​

Social providers like Google or Facebook provide basic profile data, but you can capture additional details:

location → location
homepage → website
bio → about_me

Multi-Provider Setup​

Different providers may use different claim names for the same data. Configure each provider independently:

Google OAuth:

  • firstName → given_name
  • lastName → family_name

GitHub OAuth:

  • location → location
  • homepage → blog
  • bio → bio

Technical Details​

When a user authenticates through OAuth:

  1. Casdoor receives the OAuth token and fetches user info from the provider
  2. The provider response includes standard fields plus extra claims
  3. Standard fields (username, email, etc.) are processed first
  4. User mapping rules are applied to populate additional fields from extra claims
  5. All raw claims are stored in the user's OAuth extra data for reference

This ensures that user profiles in Casdoor stay synchronized with your identity provider while maintaining flexibility in how data is structured.