Skip to main content
Version: On prem: 15.0.0

Data interfaces

Data is imported into Omada Identity using standard data collectors. Out-of-the-box, Omada Identity provides a wide range of collectors.

Data is provisioned to target systems using the Omada Provisioning Service (OPS), which comes with a wide range of standard connectors as default.

There are many standard data collectors in Omada Identity.

Data collectors​

The following is a list of example standard data collectors in Omada Identity:

  • AWS
  • Azure Management
  • CyberArk
  • Microsoft Active Directory
  • Microsoft Azure Active Directory
  • Microsoft Exchange
  • Generic Database (MS SQL and Oracle)
  • Google G Suite
  • LDAP
  • .NET Query
  • OData Service
  • REST
  • Salesforce
  • SAP SuccessFactors
  • SAP HCM
  • SCIM 2.0
  • ServiceNow
  • SOAP
  • Workday

Provisioning connectors​

Omada Identity provides the following standard provisioning connectors:

  • SAP
  • Active Directory
  • Microsoft Exchange
  • Generic PowerShell
  • Generic REST
  • Azure Active Directory
  • Azure Management
  • Salesforce
  • Generic Database (MS SQL and Oracle)
  • LDAP
  • .NET Query
  • SCIM 2.0
  • ServiceNow

Other concepts in data interfaces​

Service Catalog Application for ServiceNow​

Omada provides the Service Catalog app for ServiceNow to all ServiceNow customers that wish to integrate Omada into their ServiceNow application. The application allows users to submit access requests from the native ServiceNow interface.

Data exchange​

Using data exchanges, authorized users can import data from LDAP directories, .csv files, or MS SQL databases into Omada Identity.

Also, data can be imported by data object type and attribute mapping can be defined. This is a common interface to initially load data into Omada Identity.

You can find Data exchange in the Connectivity menu in the Omada Identity portal.

GraphQL API​

Omada Identity customers can integrate IGA workflows directly within other clients through Omada GraphQL API.

The GraphQL API is built for business logic which is used for integration with third party portals such as ServiceNow.

GraphQL is better suited as a client API as it can return more data in one request, for example, Identity, Context, Reason, Resources.

REST API​

Representational State Transfer (REST) is a simple stateless architectural pattern based on the HTTP protocol and JSON data.

REST emphasizes that interactions between clients and services are improved by having a limited number of operations. Omada Identity provides a REST API based on OData 4.0.

Flexibility is provided by assigning resources with their own unique universal resource indicators (URIs). As each operation (GET, POST, PUT, PATCH and DELETE) has a specific meaning, REST avoids ambiguity.

RESTful web services offer several advantages, for example:

  • Support for different HTTP methods to perform different actions
  • Detailed response codes and header information
  • Pagination support for large data sets

The API has two endpoints: one for built-in object types and one for data objects.

The full specification of the API is available here: OData (REST) API.

DataObject Exchange Web Service​

Omada Identity provides a Web Service where external systems with appropriate permission can read and write data in Omada Identity.