The users table we created as a demo are imported from the template XLSX file.
Click the Syncers tab and create a new syncer. Fill in all the required information as below and save.
In general, you need to fill in at least the
Name in Casdoor Columns. And others important fields like
The following are the required fields.
Organization: The organization that the user will import
Name: The syncer name
Type: Select database
Host: The original database host
Port: The original database port
User: The original database username
Password: The original database password
Database type: All Xorm supported databases, like: MySQL, PostgreSQL, SQL Server, Oracle, Sqlite
Database: The original database name
Table: The original user table name
Column name: The original user column name
Column type: The original user column type
Casdoor Column: The casdoor user column name
Is hashed: Whether to calculate hash value. When enable "Is hashed", if the field of user in origin table updated, the syncer will sync this user. Disable "Is hashed", meaning if only the field update, the syncer need not sync the user. In short, the user does not synchronize until the fields involved in the hash calculation(enable "Is hashed") are updated.
Avatar base URL: When sync users, if Avatar base URL is not empty and origin user.avatar not hasPrefix "http", new user.avatar will be replaced by Avatar base URL + user.avatar.
Affiliation table: It is used to sync the affiliation of user from this table in database. Because the affiliation may be code of int type in "Affiliation table", so we need to map the int to a string. See getAffiliationMap() . Because Casdoor has some redundant fields to borrow, here we use
scoreto map the int code to a string name.
Then you can turn on the Is enable button and save, the syncer will start to work.