Version 2022.11.1

What's improved

Searching for users now includes userName

• On the "Users > Management" page we already searched for email address, first name or last name by entering at least 3 characters. We have now added userName as part of this search for customers that use this attribute as an identifying attribute.

What's fixed

The response for /api/v1/user is in the wrong format

• The functional API for creating users showed a SCIM-like response instead of a RITM response. This has now been corrected and is in-line with other API responses (e.g. /api/v1/user/{userID} and /api/v1/users/managed-identities).

Wrong error code and response for the functional "Edit user" API

• Trying to patch a user via the functional "Edit user" API leads to a 500 response status code and message if the structure memberships are incorrectly defined. We now return a more appropriate code and response if there are for example no group memberships defined and only a structure.

Applications are not sorted when managing access roles

• Application names are not sorted when trying to add them to access roles. We now sort the application names alphabetically to improve finding the correct application.

Changing the primary email address or phone number fails

• Changing a primary email address or phone number leads to a white screen (an email verification email is send though for the change primary email address case). Both scenarios for changing your primary credentials can now be fully used again in the RITM UI.

Profile data page shows incorrect warning

• When the change password page was visited and the user would then go to his profile data page we show a warning about the fact that the new password is required. The profile data page now only shows missing required attributes that are relevant for the profile data page.