Versions Compared

Old Version 27

changes.mady.by.user Technische Redaktion

Saved on

compared with

New Version 28

changes.mady.by.user Technische Redaktion

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties
hiddentrue
idrDOC

Product Version
Report Note
AssigneeMartin

Resources & Remarks

  • Version 2.4 - options" ...  "synchronousContentAnalysis": true (OKTO-4309)

Modification History

NameDateProduct VersionAction
Antje08 FEB 20212.4New page properties macro.
Antje12 FEB 20212020 WinterrDOC
Antje04 JUN 20212021 Autumngroups added
Antje12 JUL 20222022 Autumnadd YUUVIS_MANAGE_SETTINGS default role



As of Versionproduct version 2020 Winter | component version 1.0
Request MethodPUT
Response FormatHTTP status code
Required Permission

Available if listed in authorization.accesses in authentication-prod.yml and the specified access condition is matched. In the default configuration, access is granted via the YUUVIS_TENANT_ADMIN role and YUUVIS_MANAGE_SETTINGS (as of 2022 Autumn) roles.

>> AUTHENTICATION Service
Description


Excerpt
Updates the data of the user specified by id with the data passed in the request body in JSON format.


As of version 2021 Autumn, this endpoint does not allow for the assignment of the YUUVIS_SYSTEM_INTEGRATOR role to a user. If this role is passed as an entry of the roles list, the endpoint will return an error.

As of version 2022 Summer, the deactivation of users leads to an invalidation of all their active sessions (if the enabled property is changed to false).

As of version 2022 Autumn: In the default access authorization configuration, users with the YUUVIS_TENANT_ADMIN or YUUVIS_MANAGE_SETTINGS roles are allowed to use the endpoint. However, they are not allowed to assign the roles YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR to other users.

Meaning of the response status codes:


HTTP Status CodeMeaning
200 OKSuccessful, the data for the specified user have been updated.
401 UNAUTHORIZEDThe call was unauthorized.
409 CONFLICT

At least one of the following situations occurred:

  • The user name is not unique.
  • The e-mail address is not unique.
  • The e-mail address or password must be set.
  • The role {ROLE_NAME} was not found.
  • The group {GROUP_NAME} was not found.


Request Example

PUT /tenant-management/api/admin/users/a99a0bb1-2345-6c77-8901-22dee3f4a567 HTTP/1.1

Code Block
languageyml
{
  "email": "example@exampleprovider.de",
  "userName": "mrexample",
  "firstName": "Examplename",
  "lastName": "Examplesurname",
  "roles": ["role1","role2"],
  "groups": ["mygroup","specialgroup","group2"],
  "enabled": true,
  "createdTimestamp": 1555069963564
}


Response Example

200 OK

no response body

...