2024.1.1

Changes in Veza release v2024.1.1

EAC-30780: For improved readability, dashboards now use a 2-column view when the Duration is one year.

EAC-30415: Added an internal setting to optionally hide risk levels for query results, for improved performance when searching across large environments.

EAC-30805 Sign-off on rejected rows can now trigger Jira ticket creation using orchestration actions.
EAC-30593: Added support for sorting Certification results based on the contents of the Summary Entities column.

EAC-30501 AWS: The local user for AWS database discovery no longer needs to have the same username as the AWS IAM user configured for the AWS integration. Administrators can specify any Redshift DB User, RDS MySQL DB User, or RDS PostgreSQL DB User when configuring an AWS integration.
EAC-30162 Okta: Added an option for authenticating with Okta using OAuth 2.0 client credentials (private keys), as an alternative to API tokens.
FR-1673 Salesforce: Salesforce users now have the department attribute.

EAC-30199: Access Intelligence: Non-root teams can now access the Overview page and Analysis section, restricted to integrations in the team scope.

Last updated 3 months ago