Version 2023.06.3

What's fixed

Deleting an application category would not delete this category from applications

• Deleting an application category via the functional API does not delete this category from all the applications where this category is referenced. We now properly remove the category from the applications when a category is removed via either the functional API or via the RITM UI.

Deleting an application role would not delete this role from access roles

• Deleting an application role, either via the functional API or via the RITM UI does not delete this application role from all the access roles where this application role is referenced. Removing an application role will now correctly remove any reference from the access roles.

Deleting an application would not delete this application from access roles

• Deleting an application, either via the functional API or via the RITM UI does not delete this application from all the access roles where this application is referenced. Deleting an application will now correctly remove any reference from the access roles.

Filtering on some attributes in the UI doesn't work

• In case a customer environment has been configured to be able to manage a lot of users (500 thousand or more), some attributes could not be filtered for on the "Users > Management" page. This issue has been fixed so that regardless of the configuration we will filter on the attribute values as intended.

Changes to users would sometimes need a refresh in the UI to show

• Customers would sometimes need to perform a refresh on the "Users > Management" page in the UI after a user has been updated. We have improved the update of the users on the "Users > Management" page so that a refresh should not be needed anymore after an update of a user.

Creating an admin role via the functional API would sometimes fail

• When trying to create an admin role with an entitlement and a scope for a child in a nested structure, we would sometimes show an error in the API response. The issue has been fixed so that any type of entitlement scope can be used again.