Перейти к основному содержанию

Обзор

Свойства пользователя​

As an authentication platform, Casdoor manages user accounts. У каждого пользователя есть следующие свойства:

  • Owner: Организация, которая владеет пользователем
  • Name: Уникальное имя пользователя
  • ВремяСоздания
  • ВремяОбновления
  • Id: Уникальный идентификатор для каждого пользователя
  • Type
  • Password
  • PasswordSalt
  • PasswordOptions: Опции сложности пароля
  • DisplayName: Отображается в пользовательском интерфейсе
  • Имя
  • Фамилия
  • Avatar: Ссылка на аватар пользователя
  • PermanentAvatar
  • Email
  • Телефон
  • Местоположение
  • Адрес
  • Принадлежность
  • Заголовок
  • ТипИдентификационнойКарты
  • ИдентификационнаяКарта
  • RealName: The user's verified real name (becomes read-only after identity verification)
  • IsVerified: Indicates whether the user has completed identity verification through an ID Verification provider
  • ДомашняяСтраница
  • Биография
  • Тег
  • Регион
  • Язык
  • Пол
  • ДеньРождения
  • Образование
  • Balance: The user's account balance
  • Оценка
  • Карма
  • Рейтинг
  • ЯвляетсяСтандартнымАватаром
  • ВСети
  • IsAdmin: Indicates whether the user is an administrator of their organization
  • IsGlobalAdmin: Indicates whether the user has permission to manage Casdoor
  • Запрещено
  • IsDeleted: When a user is soft-deleted (IsDeleted = true), they cannot sign in through any authentication method, including OAuth providers. This prevents deleted users from re-registering via third-party login.
  • ЗаявкаНаРегистрацию
  • Хэш
  • ПредХэш
  • СозданныйIp
  • ВремяПоследнегоВхода
  • IpПоследнегоВхода
  • Roles: An array of the user's roles (extended field, read-only via User API)
  • Permissions: An array of the user's permissions (extended field, read-only via User API)

Уникальные идентификаторы для входа через социальные платформы:

  • Github
  • Google
  • QQ
  • WeChat
  • Facebook
  • DingTalk
  • Weibo
  • Gitee
  • LinkedIn
  • Wecom
  • Lark
  • Gitlab
  • Adfs
  • Baidu
  • Casdoor
  • Infoflow
  • Apple
  • Azure AD
  • Azure AD B2C
  • Slack
  • Steam
  • Ldap

Organization Admin Privileges​

Users with IsAdmin set to true have administrator privileges within their organization:

  • Full access to manage users, applications, and resources within their organization
  • Access to verification code records sent to users in their organization
  • Ability to configure organization-level settings and policies

Organization admins have elevated permissions but are scoped to their organization only. Global admins (built-in organization users) have full access across all organizations in the Casdoor instance.

User Tags​

The Tag field allows you to categorize users for different purposes. Casdoor uses specific tag values for special user types:

  • normal-user: Standard users with full authentication capabilities
  • guest-user: Temporary users created through guest authentication without initial credentials
    • Automatically upgrade to normal-user when they set a proper username or password
    • Cannot sign in directly until they upgrade their account

You can also define custom tags to restrict application access. See Application Tags for more information.

Identity Verification​

Casdoor supports real-world identity verification through ID Verification providers. Users can verify their identity by submitting their ID card information and real name, which gets validated through third-party services like Jumio.

When a user completes identity verification:

  • The IsVerified field is set to true
  • The RealName, IdCardType, IdCard, and related identity fields become read-only
  • The verified status is included in JWT tokens and OIDC userinfo responses
  • A verification badge appears on the user's profile

This feature is useful for applications that require KYC (Know Your Customer) compliance or need to ensure user identity authenticity. See ID Verification Providers for more information on configuring identity verification.

Email Normalization​

Casdoor normalizes all email addresses to lowercase to ensure uniqueness and prevent duplicate accounts. This means that user@example.com, User@Example.com, and USER@EXAMPLE.COM are treated as the same email address, complying with RFC 5321 standards.

This normalization happens automatically during:

  • User signup and account creation
  • User login and authentication
  • Email duplicate checking

Understanding Roles and Permissions Fields​

The Roles and Permissions fields in the User object are extended fields that are dynamically populated when retrieving user data. These fields are not stored directly in the User table but are collected from the Roles and Permissions resources through the ExtendUserWithRolesAndPermissions() function.

Important: You cannot update roles and permissions through the /api/update-user endpoint, even when using the columns parameter. To manage user roles and permissions, you must use the dedicated APIs for Roles and Permissions resources.

To assign roles or permissions to users:

  • Roles: Use the Roles API endpoints to create and assign roles. Visit the Roles management page (e.g., https://door.casdoor.com/roles) or use the roles API.
  • Permissions: Use the Permissions API endpoints to create and assign permissions. Visit the Permissions management page (e.g., https://door.casdoor.com/permissions) or use the permissions API.

Using the Properties Field​

The Properties field is a flexible key-value map (map[string]string) that allows you to store custom attributes for users beyond the predefined fields in the User schema. This is particularly useful when you need to:

  • Store organization-specific user attributes
  • Add custom metadata that doesn't fit into standard fields
  • Extend user profiles without modifying the core schema

Импорт пользователей из файла XLSX​

Вы можете добавить новых пользователей или обновить существующих пользователей Casdoor, загрузив файл XLSX с информацией о пользователях.

Getting Started​

In the Admin Console, navigate to the Users page. You'll find two buttons for bulk user operations:

  • Download template: Generates an XLSX template with all available user fields and their localized column headers
  • Upload (.xlsx): Opens the upload dialog to import users from your XLSX file

Импорт пользователей

The template file includes headers in the format Display Name#field_name (e.g., Organization#owner), where the display name is localized to your language and the field name after # is used for import mapping. The comment prefix (everything before #) is automatically removed during import.

Upload Process​

When you select an XLSX file, Casdoor displays a preview modal showing all the data to be imported. This allows you to review and verify the information before final submission. Once you confirm, click the upload button to import the users.

We also provide a sample XLSX file named user_test.xlsx in the xlsx folder with 5 test users for reference.

Импорт успешно выполнен

Upload Permissions​

User upload permissions depend on your admin role:

  • Global admins (users in the built-in organization with IsGlobalAdmin set to true) can upload users to any organization. The target organization is determined by the Owner field in the XLSX file.
  • Organization admins (users with IsAdmin set to true) can only upload users to their own organization. The system ensures that duplicate checking and user creation are scoped to the correct organization.

Обход шифрования пароля​

При миграции пользователей из внешней базы данных в Casdoor могут возникнуть ситуации, когда вы хотите обойти или контролировать стандартный метод шифрования, предоставляемый методом типа пароля organization по умолчанию.

Это можно достичь, используя поле passwordType при импорте пользователя.

заметка

Пользователь с паролем Bycrypt

Ниже приведен пример тела запроса POST для маршрута API /api/add-user.

{
  "owner": "organization",
    "signupApplication": "first-app",
    "email":"dev@dev.com",
    "name": "dev",
    "displayName": "developper",
    "password": "$2a$10$.o/iVyDE9Xk8ioywHDnQRu72RviOi6FPa1ujhusbSCZeg7VOa6MY6",
    "passwordType":"bcrypt",
}

Здесь пароль пользователя уже зашифрован с использованием алгоритма bcrypt, поэтому мы указываем passwordType как "bcrypt", чтобы сообщить Casdoor, что его не нужно шифровать снова.