2024.1.22

Changes in Veza release v2024.1.22

EAC-23820 Improved Usability For Authorization Entities Sourced From OAA Integrations: Entities created with Open Authorization API (OAA) no longer have generic types such as Custom User or Custom Group. You can now create Access Reviews involving these entities as though they were sourced from a built-in integration (e.g. ZenDesk User, Trello User).
- Note: As part of this release, Workflow queries are converted to use the new entity types. For any custom applications that cannot be migrated, the Workflow query will change from Custom Resource for <Custom App> to Custom Resources (For All Apps). If this occurs and the updated query does not meet your use case, you should recreate the impacted Workflows or contact Veza customer support.

EAC-30509 Graph Optimizations: Significantly improved performance for Graph searches on Workday Security Group > Workday Domain Security Policy.

EAC-31170 Blackline: New integration for discovering Users, Teams, and Roles on the Blackline financial automation platform.

EAC-30551 Jira Configurable Fields: Jira orchestration actions can now create issues with additional system and custom fields. These optional, additional fields are enabled in a new tab when configuring the orchestration action. Tickets can be created with user-defined values for a limited set of System Fields (e.g. Component), and custom fields based on the specified field, type, and value. Please contact support if your use case requires additional system fields or field types.
EAC-31118 Custom Identity Mapping for OAA Apps: Custom Identity Mappings for specifying relationships between local accounts on different platforms or apps can now use custom properties for Open Authorization API-based integrations.
EAC-31441 BambooHR: Integration configurations can now include the IdP types for connecting employees to authorization providers. This should be a comma-separated list of providers, e.g. okta, onelogin.
EAC-31048 Improved Formatting for Jira Alerts: Jira issues created by Rules and Alerts now have an improved Description format intended for easier human readability. The original JSON is now included as a file attachment to these issues.

EAC-30883: Notifications sent when performing the Test function on an Orchestration Action no longer include the legacy term Cookie, and instead now use the company name Veza.
EAC-31406: Fixed an issue where the Test function in the Edit Orchestration Action flow failed to perform the test when any configured secrets (password, token, etc.) were left unmodified.
FR-1745 Microsoft Azure Management Group IAM Permissions: Veza now shows role assignments and their effective permissions for Azure Management Groups. This provides a more accurate visualization of access when granted by either a Management Group assignment or an assignment on the Azure Subscription, in System and Effective search mode.

EAC-30661 System Settings: Added an option to toggle redirection of visitors on the Veza home page to your Single Sign-On provider for log-in. This option currently appears only when SSO Auto-Redirect is enabled as an optional feature.
EAC-31496 Sign-In Settings Authorization namespace configurations (Early Access) are now on the Sign-In Settings page, instead of under System Settings.

Last updated 3 months ago