Schema Reference

The application schema is used to configure the objects returned from a connector.

The Coupa SaaS connector uses the following default correlation and object configurations.

Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to Assigning Source Accounts to Identities for more information.

When you first create the Coupa SaaS source, the default correlation mapping is:

You can modify the correlation configuration in accordance with your requirements.

Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.

Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.

The following table lists the default account IDs for this connector:

Default Account Attributes

The Coupa SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

[
  {
    "op": "add",
    "path": "/connectorAttributes/customLicenseAttributes",
    "value": ["<custom license attribute 1>", "<custom license attribute 2>"]
  }
]

Account Schema Extension for Standard and Custom Attributes

Configure the connector to include custom attributes from the source in account aggregation processes. To include additional custom attributes in the account aggregation processes, add the attribute name to the account schema exactly as it is configured in the source schema.

If you want to extend the default account schema and provisioning policy to manage other standard or custom attributes, you can use either of the following methods. When you add attributes to a default schema, whether they are standard or custom, you are extending the schema.

During account aggregation, the connector uses the default filter, return_object=shallow. If the aggregated data for custom attributes is incomplete using the default filter, then you need to add the return_object=full filter to the Account Filter field on the Aggregation Settings page.

For example, if the existing account filter is type[blank]=true and you need to fetch more data through the API as a result of extending the schema, then you can update the filter to type[blank]=true&return_object=full.

On the downside, adding the return_object=full filter degrades aggregation performance, since fetching full objects results in an increase in API response time and size. SailPoint recommends that you add schema attributes that require the full account filter only if they are critical for deployment.

Method 1

Add attributes returned by the /users API. The following are examples for standard, complex, and custom attributes:

• Standard Attributes - To add a mobile phone number for a user, define the phone-mobile attribute in the account schema and the provisioning policy.

• Complex Attributes - You can use "dot walking" to navigate to the field you want to include in the account schema or the provisioning policy. The following are examples for using dot walking:

  • To add the name of a country of residence, define country-of-residence.name as the field name in the schema and provisioning policy.
  • To show the country code for country of residence, define country-of-residence.code as the field name in the schema and provisioning policy.

• Custom Attributes - If it is a complex attribute, use dot walking to navigate to the field you are interested in using. Use the following format:

  custom-fields.<field_name>
  

  For example, if designation is a custom attribute in your Coupa tenant, then add the custom-fields.designation attribute to the account schema and account provisioning policy.

Method 2

Add a JSONPath (JPath) based mapping to the connector in the customUserObjectMapping field.

For example, if you want to add definitions for the roles (standard attribute) and designation (custom attribute) attributes, you can map them to your connector using the following:

<entry key="customUserObjectMapping">
    <value>
        <Map>
            <entry key="roles" value="roles[*].name"/>
            <entry key="designation" value="custom-fields.designation"/>
        </Map>
    </value>
</entry>

Then you can update the account schema and account provisioning policy with just the name of the attribute. For example, roles or designation as a string type entry.

Default Role Attributes

The Coupa SaaS connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.