Integrations

Overview of supported Lifecycle Management integrations in Veza, with capabilities and supported actions for target applications and sources of identity.

Overview

This document provides an introduction to the integrations supported by Veza Lifecycle Management (LCM), including capabilities and supported actions. These integrations enable automated identity and access management workflows across a wide range of identity sources and target applications.

Lifecycle Management supports three primary implementation pathways:

  1. Native Integrations - Direct API-based provisioning with out-of-the-box support (see validated integrations below)

  2. SCIM 2.0 Protocol - Standards-based provisioning for any SCIM-compliant application

  3. OAA Write Framework - Veza's Open Authorization API (OAA) can support provisioning and deprovisioning for applications not natively supported by the Veza platform.

This architecture means that nearly any existing Veza integration can be enabled for Lifecycle Management. The validated integrations listed below represent tested, production-ready configurations. For additional integration support, contact your Customer Success Manager.

Supported Integrations

Identity Sources

Identity sources are authoritative systems that provide information about user identities. While Veza does not require write permissions to the identity source of truth, some of these integrations are also supported as provisioning targets. Integrations can also allow write-back of a user's newly created email address to the user's record in the source of identity as part of the initial provisioning workflow.

Lifecycle Management supports leading HR systems, IDPs and directory services, ITSM platforms, payroll systems, custom applications, and flat files:

Identity Source
Supported Entity Types
Notes

ActiveDirectoryUser

CustomHRISEmployee

CustomHRISEmployee

CustomIDPUser

CustomHRISEmployee

CustomHRISEmployee

Supports email write-back

CustomHRISEmployee

AzureADUser

OktaUser

OAA.Oracle HCM.HRISEmployee

Supports email write-back

ServiceNowUser

CustomHRISEmployee

WorkdayWorker

Supports email write-back

Target Application Support

The entire catalog of Veza application integrations is Lifecycle Management-ready. Target application support in Lifecycle Management leverages Veza's existing native and OAA-based integrations, plus an intelligent shim layer to provide support for provisioning and de-provisioning.

As such, target application support in Lifecycle Management can be enabled for nearly every Veza-supported integration.

Validated Integrations

The following table lists the out-of-the-box, Veza-validated target application integrations for Lifecycle Management.

Target Application
Manage Relationships
Sync Identities
Deprovision Identity
Additional Actions
Supported Entitlement Types
Notes

Reset Password, Create Entitlements, Delete Identity

ActiveDirectoryGroup

-

Delete Identity

AtlassianCloudAdminGroup

-

Create Entitlement

AwsSsoGroup

-

Create & Manage Email, Create Entitlement

AzureADGroup, AzureADRole, ExchangeOnlineDistributionGroup, AzureADLicense

Email management includes mailbox configuration (size limits, quotas, auditing) and client access settings (OWA, ActiveSync, MAPI, POP, IMAP)

Delete Identity

ApplicationGroup, ApplicationRole

-

Create Email

-

-

-

GithubOrganization, GithubTeam

-

-

GoogleWorkspaceGroup

-

Delete Identity

MySQLRoleInstance

-

Reset Password, Create Entitlement

OktaGroup

Supports two deprovision types: SUSPENDED (temporary) and DISABLED (permanent deactivation)

Delete Identity

OracleDBRole

-

Delete Identity

OracleRole

-

-

-

-

Delete Identity

PagerDutyTeam

Platform does not support user deactivation; use Delete Identity instead

Delete Identity

PostgreSQLGroup

-

-

SalesforceGroup, SalesforcePermissionSet, SalesforcePermissionSetGroup, SalesforceProfile, SalesforceUserRole

-

SAP ECC

-

SapEccRole

-

-

-

-

Custom Action

-

-

-

SnowflakeRole

-

Delete Identity

SplunkEnterpriseRole

Platform does not support user deactivation; use Delete Identity instead

-

WorkdaySecurityGroup

-

Veza

-

VezaRoleBinding, VezaAccessProfile, VezaGroup

-

Other Supported Integrations

For any Veza-supported application not listed above, contact your Customer Success Manager for more details on how to enable the specific Veza integration for use with Lifecycle Management as a target application for provisioning and de-provisioning.

Custom REST Actions

Lifecycle Management supports Custom REST Actions that enable HTTP requests to external APIs and services as part of LCM workflows. This action type provides integration with custom applications, webhooks, and any REST-based service that supports identity management operations.

Custom REST Actions extend LCM support to virtually any system with an accessible API, enabling use cases such as triggering custom workflows, notifying external systems, or coordinating provisioning sequences across multiple downstream applications.

Configuring Integrations for Lifecycle Management

Insight Points for Lifecycle Management

An Insight Point is required to enable Lifecycle Management operations and identity discovery for systems that Veza cannot access directly, such as an on-premises application server behind a firewall. The Insight Point is a lightweight connector that runs in your environment, enabling secure gathering and processing of authorization metadata for LCM tasks.

A Veza Insight Point is typically deployed as a Docker container or VM OVA, running within your network for metadata discovery and LCM job execution. This ensures secure communication between your environment and Veza.

For deployment instructions, refer to the Insight Point Documentation.

Scheduled and Manual Extractions

You can configure extraction intervals for your integrations to ensure data is regularly updated for Lifecycle Management processes.

  1. Go to Veza Administration > System Settings

  2. In the Pipeline > Extraction Interval section, set the global extraction interval

  3. To override the global setting for specific integrations, use the Active Overrides section

Available extraction intervals are:

  • Auto (hourly, but may take longer when the extraction pipeline is full)

  • 15 Minutes

  • 1 Hour

  • 6 Hours

  • 12 Hours

  • 1 Day

  • 2 Days

  • 3 Days

  • 7 Days

  • 30 Days

To manually trigger an extraction:

  1. Go to Integrations > All Data Sources

  2. Search for the desired data source

  3. Select Actions > Start Extraction

Note: Custom application payloads are extracted after the payload is pushed to Veza using the Open Authorization API.

Enabling Lifecycle Management

To enable Lifecycle Management for a specific integration:

  1. Browse to the main Veza Integrations page, or go to Lifecycle Management > Integrations

  2. Search for the integration you want to enable

  3. Toggle the Lifecycle Management option to Enabled

Managing integrations for Lifecycle Management

Checking on Lifecycle Management Data Sources

To verify the health of the Lifecycle Management data source:

  1. Use the main Veza navigation menu to open the Lifecycle Management > Integrations page or the Veza Integrations overview

  2. Search for the integration and click the name to view details

  3. In the Properties panel, click the magnifying glass icon under Lifecycle Management Enabled

Additional Resources

For more information:

  • Refer to individual integration documentation for detailed LCM capabilities

  • Consult the Lifecycle Management user guide for troubleshooting and best practices

  • Contact Veza support for assistance with enabling or configuring LCM for your integrations

Last updated

Was this helpful?