Skip to main content
Sign in

Creating an extended integration for DISCO Hold - Google Vault and Workday users

  • November 13, 2024 14:08
  • Updated

Let Oomnitza be your single source of truth!

You can track Workday user information and the information that is on hold in Google Vault.

There are two DiscoHold integrations with Oomnitza, the DISCO Hold User Load and the DiscoHold with Google Vault User Load. Both user loads use the same API, however, there is additional Google Vault mappings/information returned in the Google Vault User Load.

Connect Oomnitza and DISCO Hold in minutes

Get the information and insights that you need to reduce costs and the time that you spend on administration tasks such as:

  • Configurable dashboards and list views of the legal hold status of Workday information stored in Google Vault
  • Configurable reports to share information about Workday users 

Tip
Because of account-specific mappings in DISCO Hold, contact your customer success manager or support@oomnitza.com to integrate DISCO Hold with Oomnitza.

Before you start

For the integration with Oomnitza, you must supply the following information:

Client ID and Client Secret

To stream DISCO Hold data into Oomnitza, you must add OAuth 2.0 credentials to the credentials vault in Oomnitza. To do this, you request OAuth 2.0 credentials from your support team in DISCO Hold. When you get the credentials, you can add them to the Oomnitza vault.

Customer domain

For example, your URL is https://www.myexample.com. In this case, you enter the highlighted part of the URL, which is myexample.

API version

For the API version, enter 1.3.

Add credentials to the vault in Oomnitza

To authorize connections between Oomnitza and DISCO Hold, you must add the OAuth 2.0 credentials that you received for DISCO Hold to the credentials vault in Oomnitza.

  1. In Oomnitza, click Configuration > Security > Credentials.
  2. Click Add new credential (+).
  3. Search for the integration, and then click the forward arrow > to select the integration. 
  4. Enter your client credentials and any other additional information.
  5. Click Authenticate. You are prompted to log in to authorize your request.
  6. Click CREATE.
  1. On the INFORMATION tab, complete these actions:
    1. Add the name of the credential.
    2. Add the name of the owner. 
  2. Ensure that OAuth 2.0 is selected as the Authorization type.
  3. Ensure that DISCO Hold is selected from the SaaS list.
  4. Enter your Customer Domain, Client ID, and Client Secret.
  5. Click Authenticate. You are prompted to log in to DiscoHold to authorize your request.
  6. Click CREATE.

Next step

You use the credentials that you added to create and customize your DISCO Hold integration with Oomnitza.

Integrate DISCO Hold with Oomnitza

  1. In Oomnitza, click Configuration > Integrations > Overview.
  2. Click Block view block_view.PNG.
  3. On the Integrations page, scroll down to the Extended section for user integrations.
  4. Click NEW INTEGRATION.
  5. In the sidebar, search for the integration.
  6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

  • User only. Add user records.
  • User plus SaaS user. Add user and SaaS user records. 

The benefit of adding SaaS user records is that you can run a workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that can be retrieved depends on whether SaaS user workflows are available for the integration. 

Installation types

  • Cloud. Store credentials in the Oomnitza cloud.
  • Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

  • Create & Update. Add and update records.
  • Create only. Add records.
  • Update only. Update records.

Editing the integration details

  1. Click Edit edit_black_pencil_icon.svg.
  2. Make your changes.

Editing the credential details

If you selected Cloud as the installation type, choose one of the following options:

  • Select the credentials that were created for the integration.
  • Edit the credentials that were created for the integration.
  • Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

  1. Click Edit edit_black_pencil_icon.svg.
  2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit edit_black_pencil_icon.svg.

 cog_red_dot_small_icon.svg Selecting Edit integration to add rules for syncing data. small_blue_link.svg Filtering integration results.  
 

You can add new fields to your integration by selecting Add new field  add_grey_rectangel_icon.svg on the mapping page. 
small_blue_link.svg Creating custom API fields. 

Creating custom mappings

Map the DISCO Hold fields to Oomnitza fields and create custom mappings to get the information that you need to track and manage your user information.

Complete these actions:

  1. Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
  2. Create a custom mapping for the User ID. To do this, complete the following steps:
    1. Select the down arrow on the ID field that you want to map.
    2. Select Add new Oomnitza users field.
    3. Change the name of the field to DISCO Hold User Id.
    4. Select the Unique checkbox.
    5. Click CREATE. 
  3. Ensure that the Email is mapped to the
    1. Username field on the Oomnitza side (required for integration).
    2. Email field on the Oomnitza side (required for integration).
  4. Select the Role field on the Oomnitza mapping side.
  5. Choose a suitable role from the list (a defined role is necessary for the integration)
  6. Assign a sync key to a unique field, such as the Email.
  7. Click UPDATE.

DISCO Hold User Load

Asset
Domain
Connector Sync Time
Email
Google Vault Identity
Google Vault Source Data String
Google Vault Type
Name
OnHold
User ID
Workday Department
Workday Duration
Workday Identity
Workday Job Title
Workday Last Day Of Work
Workday Manager Email
Workday Manager Name
Workday Preferred Name
Workday Start Date
Workday Termination Date

DiscoHold with Google Vault User Load

Asset
Domain
Connector Sync Time
Email
Id
Name
On Hold
Google Vault Identity
Google Vault Source Data License Data Etags
Google Vault Source Data License Data Kind
Google Vault Source Data License Data Product Id
Google Vault Source Data License Data Product Name
Google Vault Source Data License Data Self Link
Google Vault Source Data License Data Sku Id
Google Vault Source Data License Data Sku Name
Google Vault Source Data License Data User Id
Google Vault Source Data User Data Addresses Formatted
Google Vault Source Data User Data Addresses Type
Google Vault Source Data User Data Agreed To Terms
Google Vault Source Data User Data Aliases List
Google Vault Source Data User Data Archived
Google Vault Source Data User Data Change Password At Next Login
Google Vault Source Data User Data Creation Time Date Only
Google Vault Source Data User Data Creation Time Time Zone Shift
Google Vault Source Data User Data Creation Time Value
Google Vault Source Data User Data Customer Id
Google Vault Source Data User Data Emails Address
Google Vault Source Data User Data Emails Primary
Google Vault Source Data User Data Etag
Google Vault Source Data User Data External Ids Type
Google Vault Source Data User Data External Ids Value
Google Vault Source Data User Data Gender Type
Google Vault Source Data User Data Id
Google Vault Source Data User Data Include In Global Address List
Google Vault Source Data User Data Ip Whitelisted
Google Vault Source Data User Data Is Admin
Google Vault Source Data User Data Is Delegated Admin
Google Vault Source Data User Data Is Enforced In2Sv
Google Vault Source Data User Data Is Enrolled In2Sv
Google Vault Source Data User Data Is Mailbox Setup
Google Vault Source Data User Data Kind
Google Vault Source Data User Data Last Login Time Date Only
Google Vault Source Data User Data Last Login Time Time Zone Shift
Google Vault Source Data User Data Last Login Time Value
Google Vault Source Data User Data Name Family Name
Google Vault Source Data User Data Name Full Name
Google Vault Source Data User Data Name Given Name
Google Vault Source Data User Data Notes Value
Google Vault Source Data User Data Org Unit Path
Google Vault Source Data User Data Organizations Custom Type
Google Vault Source Data User Data Organizations Department
Google Vault Source Data User Data Organizations Primary
Google Vault Source Data User Data Primary Email
Google Vault Source Data User Data Recovery Phone
Google Vault Source Data User Data Relations Type
Google Vault Source Data User Data Relations Value
Google Vault Source Data User Data Suspended
Google Vault Source Data User Data Suspension Reason
Google Vault Source Data User Data Thumbnail Photo Etag
Sources Google Vault Source Data User Data Thumbnail Photo Url
Google Vault Subtype
Workday Identity
Workday Source Data Department
Workday Source Data Duration
Workday Source Data Job Title
Workday Source Data Last Day Of Work
Workday Source Data Manager Email
Workday Source Data Manager Name
Workday Source Data Preferred Name
Workday Source Data Start Date
Workday Source Data Termination Date
Workday Subtype

Need another DISCO Hold integration?
This integration streams Google Vault and Workday user information from DISCO Hold to Oomnitza. If you need to manage other information from DISCO Hold, contact support@oomnitza.com.

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

small_blue_link.svg If you selected Cloud as the installation type when creating the integration, see Running an extended integration

small_blue_link.svg If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

Unleash the power of Oomnitza

To get valuable actionable insights that help you manage your assets, learn how to:

  • Configure dashboards for your users and software
  • Configure custom reports about your users and software
  • Create workflows to automate tasks

See Getting started for more information.

Related articles

Comments

0 comments

Please sign in to leave a comment.