Version 2022.07.0

What's fixed

Potential entitlement issues for users with multiple email addresses

• We used to search the identity store by looking for a user's email address which could lead, in some edge cases, to the wrong entitlements. This particular search is now based on the user id of the user, which is always unique and this makes sure that the entitlements are what is assigned to them.

Removing groups and/or roles through mass updates does not work

• Adding groups and/or roles was working fine but deleting them did not work as expected. You can now use mass updates again to remove both groups and/or roles.

Showing a page with roles can be very slow

• On the roles page, we show the number of users with this role assignment and the user who created the role. If the user who created the role in the past is not longer in the identity store this would lead to a slow behaviour when rendering the page. Especially when there were more roles created by a user that was removed. The pages are now rendered fast again as they should.

Resetting the platform menu to default shows too many items

• If you have moved items around in the menu and want to return to the default, too many menu items would be shown that are not relevant to your organisation. We now only show the relevant menu items when resetting the platform menu to the default.

/api/v1/users/managed-identities gives wrong response for some multi-valued attributes

• The functional API for retrieving managed identities showed some multi-valued attributes twice in the response. This has now been fixed to only show these attributes in the correct schema extension object.

/api/v1/user/{userID} appears to fail when updating user information

• The functional API for updating users, sometimes showed an error code and message, even though the actual update was performed. We now show the proper response when updating a user that has some complex attributes as part of his profile.