2024.3.25

Changes in Veza release v2024.3.25

EAC-33189: Improved readability within the Row Details drawer. It is now easier to see which table cell value belongs to which entity group for a result.
EAC-15565: Improved performance of the Access Reviews certification table, especially when selecting table rows.

EAC-33311: Fixed an issue where some system permissions were not included in the Effective Permissions shown for users on Google Cloud projects.

EAC-32936 Salesforce: Veza now supports Permission Set Groups used to assign sets of permissions to teams of users. These can be related to a single Muting Permission Set entity, used to disable some or all permissions in a Permission Set Group.
EAC-32660 AWS Unsupported Condition List Property: AWS entities with the Unsupported Condition boolean property now also have an Unsupported Condition List showing any policy condition operators and keys which are not parsed by Veza.
EAC-33279 Concur: Added support for gathering user email addresses (requires additional API scope identity.user.coresensitive.read).

EAC-33282 Atlassian: Fixed an issue causing incorrect mappings for Atlassian Cloud principals and identity provider groups.
EAC-33279 Concur: Fixed an issue resulting in incorrect attributes for Concur users.
EAC-32586 AWS Role Assumption Permission Boundary Conditions: Veza now evaluates AWS policy conditions in permissions boundaries when parsing assumed roles.

EAC-32727: When adding a team, administrators can now use an All Providers checkbox to include all integrations in the team scope.
EAC-31317: The Events page now shows logins for SSO users.

Last updated 1 month ago