Version 2024.2

What's new

New search options in RITM UI for customers with many users

• The previous search on "Users > Management" or "Reports > Users" had some short-comings for customers with large number of users. Only customers that have this new functionality enabled will notice these changes. We have split the search into several options and introduced some other changes:
  • Search is no longer automatically triggered after typing 3 or more characters. You will need to press <Enter> or click on the magnifying glass to trigger a search.
  • The search no longer searches on first name, last name, user name or email-address, but rather on:
    • First name, last name and user name only when "Search names" is selected in the dropdown on the search bar.
    • The first 10 characters (we will convert to lower-case) of the email-address when "Search emails" is selected in that dropdown.

New functional API to create role requests

• A new functional API has been introduced with the ability to create one or more role requests. These requests are either for the authenticated user or as an admin on behalf of an user.

New functionality when managing dates in the RITM UI

• When choosing the "Date" option for attributes, it's now possible to configure the display format (the way that a date is shown in the RITM UI) and how the date is stored (typically in CIAM where specific rules/patterns might be required).

What's changed

The RITM UI now shows more characters of structure and group names

• Some customers use long(er) names for structures and/or groups. Especially for names where the first characters are the same it would not always be immediately clear which group memberships a user has when managing the user via "Edit user" or "Access profile". We now widened the information on the groups tabs of the mentioned pages.

What's improved

Performance improvements

• We improved the general performance of several functional API calls to RITM. For functional APIs that involves many users we sometimes used too many resources.

What's fixed

Denying role requests was not possible from the RITM UI

• It is not possible to deny role request for a managed identity via the profile page of that user. We fixed this bug and now it's possible to deny requests again from all places where an admin could manage the requests of an user.

Translations are wrong when activating/deactivating rules in the RITM UI

• When a rule was activated or deactivated we show translation codes instead of the actual text/translation. This has now been fixed so that managing rules shows the correct texts for the configured languages.

Using an invalid API key sometimes gives the wrong error message

• When using an invalid API key to call an API we sometimes show a "User not exist" error message and sometimes a "Authorized key not exist" error message. We now aligned the error handling of all use-cases to always show "Authorized key not exist" when an invalid API key is used.