Create a user in Keycloak
Manually create users if you work in local-only mode or without SSO-only configuration
読み終わるまでの所要時間 2 分最終更新 1ヶ月前
After you have set up single sign-on (SSO) for the realm, Keycloak automatically provisions an account for each user on their first sign-in via the enterprise identity provider (IdP). On subsequent sign-ins, Keycloak updates the user properties based on the information from the IdP. Nevertheless, you might need to create user accounts in Keycloak in these cases:
- You use Keycloak in local-only mode, that is, with only local users.
- You haven't applied SSO-only configuration. Read more about configuring the user experience.
To create users in Keycloak, complete these steps:
- In the Keycloak admin console, switch to the unity realm.
- Go to Manage > Users.
- Select Add user.
- Provide these settings:
|
|
|---|---|
User name | A unique name for the user. The recommended practice is the email address. |
E-mail | The user's email address. |
First name | The user's first name. |
Last name | The user's last name. |
注
If you only have the user's full name, you can enter it in either field (First name or Last name) and leave the other empty. Unity Identity only requires the full name, which is constructed from these two fields.
After you have created the user, change the configuration as follows:
- On the Credentials tab, set a password so that the user can sign in.
- Instruct the user to sign in for the first time. Refer the note hereinafter.
- Grant access to an organization and to a project.
注
The system doesn't add new users to the Asset Manager organization when creating them in Keycloak, but only during their first sign-in, with the User user type. In other words, before new users can appear as organization members in Unity Asset Manager, they must sign in first.
- This process happens seamlessly for SSO users within the same first sign-in flow via the enterprise IdP: they are automatically provisioned in Keycloak and then added to the organization right after that.
- Local users need to sign in first to be added to the organization members. Only then administrators can assign additional user types and roles to them.