2023.12.18

Changes in Veza release v2023.12.18

Access Intelligence

• EAC-30743: Dashboard views for 6 months and 1 year now show a single value for each week, instead of a value for each day.

Bug Fixes

• EAC-30711: Fixed an issue with report PDF export causing long descriptions to overlap query results.

Access Monitoring

Enhancements

• EAC-30693: AWS entities now appear on the Activity Monitoring dashboard, when the Early Access feature is enabled. See Activity Monitoring for AWS for more details.

Access Reviews

Bug Fixes

• EAC-28061: Fixed an issue with long workflow names not wrapping correctly on mobile devices.

• EAC-30627: Fixed an issue applying filters from the UI for workflow queries with multiple destination entities from OAA providers.

• EAC-30173: Improved display of attributes with long string values in the result details sidebar.

Veza Integrations

Enhancements

• EAC-39631 GitHub: Integration configurations now have repository allow and deny lists to customize which resources Veza will add to the Authorization Graph. The integration now implements concurrency for improved extraction times.

• EAC-30629 GitHub: Added support for custom repository roles for Enterprise Server environments (before, these were only available in Enterprise Cloud). GitHub configurations now have a checkbox to enable or disable gathering external repository collaborators.

• EAC-30562 Microsoft Active Directory: Veza now shows additional user attributes: City, Company, CountryCode, Description, DisplayName, PhysicalDeliveryOfficeName, PostalCode, StateOrProvinceName, SurName, GivenName, and Title.

• EAC-30550 Jira Data Center Support: The Jira Orchestration Action now supports both the Atlassian Cloud (SaaS) and Atlassian Data Center (on-premise) products. This is configurable by selecting the Atlassian Product property when configuring the integration.

Veza Platform

New features

• EAC-30202: Added support for assigning teams and roles based on an incoming SAML groups claim when users log in with Single Sign-On.

• EAC-30602: Teams can now have SSO aliases, used to map Veza teams to an Identity Provider role or group in SAML assertions.

Enhancements

• EAC-21648: Administrators can now delete unused Insight Points with no associated integrations.

• EAC-30182: When creating a local user on the User Management page, the root team is now automatically selected when it is the only available team. Administrators must now confirm before creating a user with no team assigned.