Skip to content

Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Country Code Attribute Is Not Fetched During Aggregation

Resolution: To resolve this issue, update the following entries in the Application configuration:

  1. Remove the invoicing_user attribute from the account schema:

    <AttributeDefinition name="invoicing_user" type="boolean"/>
    
  2. Update userObjectMapping:

    <entry key="country-code" value="default-address.country.code"/>
    
  3. Add country-code to the account schema:

    <AttributeDefinition name="country-code" type="string"/>
    
  4. Update accountFilter:

    <entry key="accountFilter" value="type[blank]=true&return_object=full"/>
    

Any Attributes Added to "customUserObjectMapping" with a Value Containing the Keyword "amount" Are Not Provisioned Correctly

For example:

"requisition-approval-limit": {
"amount": 999999999,
"currency": {
"code": "USD"
}

Resolution: Add the attributes that contain the "amount" value to the attrsToExcludeCurrencyCode entry to skip them during provisioning. The following example shows the entry to skip the requisition-approval-limit and expense-approval-limit that contain values with the amount keyword (as shown in the first example).

Add the entry using the REST API:

PATCH https://sailpoint.api.identitynow.com/v3/sources/:id

In the body of the PATCH, use the form-data as follows:

  • Key: attrsToExcludeCurrencyCode
  • Value: requisition-approval-limit,expense-approval-limit

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.