Create a user
Creates a BPMS 3.x user of the tenant of the request with its roles, as the 3.x user form does; the password is stored as Argon2id. Requires 6.2.2.1 (create users) and every authority of the requested roles.
bearerAuthorizationBearer <token>The token of a session that createSession opened
The new user
application/json- body
email?|Up to 255 characters; required and unique in the tenant only when bpms.access.users.email-required is on
enabled?booleanWhether the user may log in; true when absent
trueidentification?stringUp to 15 letters and digits; unique in the tenant
lastName?stringUp to 255 characters
locked?booleanWhether the user starts locked, as after too many failed logins, until it is unlocked; false when absent. The dashboard shows this box checked: that default is the dashboard's, not the API's
falsemustChangePassword?booleanWhether the user must change the password at the next login; true when absent
truename?stringUp to 255 characters
password?stringMust follow the password policy; stored as Argon2id
roleIds?array<>Ids of the roles of the tenant, at least one; the caller must hold every authority of each
userName?stringThe name the user logs in with, up to 255 characters; unique in any case
The created user; Location names it
application/json- response
email?string|nullenabled?booleanFalse when the user is disabled; a stored NULL reads as false
id?integerint64identification?stringlastName?stringlocked?booleanTrue once the failed logins exceed the configured maximum
name?stringpasswordChangeRequired?booleanTrue when the user must change the password at the next login
userName?stringThe name the user logs in with
curl -X POST 'https://bpms.bpms.work/api/v1/access/users' \ -H 'Content-Type: application/json' \ -d '{}'{ "email": "string", "enabled": true, "id": 0, "identification": "string", "lastName": "string", "locked": true, "name": "string", "passwordChangeRequired": true, "userName": "string"}