Domo
Domo is an open, self-service platform that brings together data, people, and insights that executives need to find answers to critical business questions and make faster, better-informed decisions to improve business performance. Domo connects to all the data, whether it is in spreadsheets, social platforms, MySQL, or Salesforce and enables users to filter, combine, and personalize data into visual dashboards.
The following sections explain prerequisites, resources, and instructions for integrating with SaaS Management.
• | Stored Domo Information |
• | Required Minimum Permissions for Domo |
• | Domo Authentication Method |
• | Required Domo Credentials |
• | Integrating Domo With SaaS Management |
• | Domo API Endpoints |
The following table describes the available integration tasks and stored data within [ProductName].
Available Integration Tasks |
Information Stored |
||||||||||||||||||
Application Roster |
|
||||||||||||||||||
Application Access |
|
Note:The information stored is subject to change as enhancements are made to the SaaS application.
Required Minimum Permissions for Domo
A Domo developer account is required for creating an OAuth2 client application. The minimum API required permissions are based on the Required Domo Scopes and the Required Domo User Role .
Scope |
Description |
Integration Task |
User |
This scope is required for calling the List Users API. |
Application Roster |
Audit |
This scope is required for retrieving the activities from the Audit Log API. |
Application Access |
Note:The following SaaS application user role is not applicable to Flexera One roles.
Description |
|
Admin |
The Admin role is required to fetch the activity logs. For more information, see Domo’s documentation topic, Viewing Activity Logs. Note: If you do not wish to use the Admin user role, create a custom role with the View Activity Logs checkbox enabled. To create a custom role in Domo, see Domo’s documentation topic, Creating Custom Roles. |
The required authentication method is OAuth 2.0 With Client Credentials. For more information, see DocuSign’s documentation topic, API Authentication.
The following credentials are required:
• | Client ID—An ID used to uniquely identify a third-party client |
• | Client Secret—A secret code that proves to the authentication server that the client program is authorized to make a request. |
Integrating Domo With SaaS Management
Complete the following steps to integrate Domo with SaaS Management.
To integrate Domo with SaaS Management:
1. | Copy your Domo domain, which is needed for the Domo developer account. The domain is in the format: companyname.domo.com |
Example: flexera.domo.com where flexera is the domain.
2. | Sign in to your Domo developer account at https://developer.domo.com or create a developer account at https://developer.domo.com/dev-sandbox-request |
3. | Enter your Domo domain and click Continue. |
4. | To create a new client in the Domo developer portal, go to the My Account tab and click New Client(https://developer.domo.com/new-client). The Create New Client dialog box appears. |
5. | Complete the following information in the Create New Client dialog box. |
a. | In the Name field, enter SaaS Management Connector. |
b. | Enter an application Description. |
c. | For Application Scope, select Audit and User. |
d. | Click Create. |
6. | Add the Domo application in SaaS Management. For more information, see Adding an Application. |
7. | Copy and paste the following Domo information in SaaS Management: |
• | Client ID |
• | Client Secret |
8. | Click Authorize. |
Application Roster
https://api.domo.com/v1/users
Application Access
https://api.domo.com/v1/audit