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:

Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.

Irreparable error,"status":500 when processing entities

Issue: The connector cannot process more entities due to irreparable error","status":500. This can happen if there is a space in the property file attribute.

Resolution: Go to IPS Proxy > Properties User Attribute and ensure there are no spaces in between the property file attributes.

Property has invalid syntax!","status":400 when initializing SacDelegatingReadConnector

Issue: A space is in the URL field causing the following error: connector.common.http.exception.HttpException: {"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"detail":"Can not initialize SacDelegatingReadConnector: com.sap.cloud.ips.connectors.api.ConnectorSetupException: Property has invalid syntax!","status":400}

Resolution: Ensure there are no spaces in the URL.

Java.lang.IllegalArgumentException OAuth error

Issue: A mandatory parameter is missing in properties causing the error java.lang.IllegalArgumentException: OAuth client configuration is invalid!

Resolution: Ensure all the required parameters are entered in the properties.

Execution Fails on Behalf of a Tenant Due to Missing Authentication

Issue: This error displays when authentication is missing in properties.

Resolution: Enter the Authentication type.

Request is unparsable, syntactically incorrect, or violates schema

Issue: This error can happen if you update an id that was recently added and the email address has not yet been used to sign in to the system.

Resolution: Ensure it is a valid user that has logged in with their email.

ConnectorException during Update Account or Create Account operations with large groups

Issue: The connector fails with ConnectorException errors during Update Account or Create Account operations when provisioning users to groups with a large number of members (100 or more). The following errors might appear:

java.net.SocketTimeoutException: Read timed out during Update Account operations
HTTP 409 Conflict with scimType: uniqueness and a detail message indicating the specified version number does not match the resource's latest version number during Create Account operations

Resolution: Follow these steps in order. For the SAP Analytics Cloud connector, all parameters must be prefixed with ips0_.

Add the following entry to the source XML using the REST APIs to increase the connection timeout. The value is in minutes.
```
[
  {
    "op": "add",
    "path": "/connectorAttributes/ips0_customTimeout",
    "value": "5"
  }
]
```
Test the provisioning operation again. If the issue is resolved, no further changes are needed.

If the issue persists, add the following entries to the source XML using the REST APIs one at a time. Test the provisioning operation after adding each entry.

a. Enable updating groups via users:

[
  {
    "op": "add",
    "path": "/connectorAttributes/ips0_updateGroupsViaUsers",
    "value": "true"
  }
]

b. Enable PATCH operations for accounts:

[
  {
    "op": "add",
    "path": "/connectorAttributes/ips0_usePatch",
    "value": "true"
  }
]

c. Enable PATCH operations for groups:

[
  {
    "op": "add",
    "path": "/connectorAttributes/ips0_useGroupPatch",
    "value": "true"
  }
]

Important

The ips0_ prefix is mandatory for this connector type. Without it, the keys do not take effect.

Using PATCH operations instead of PUT resolves timeout issues for large user groups. PUT operations send the entire group membership payload, which can cause timeouts from SAP IPS.

SAP IPS might return HTTP 429 (Too Many Requests) for large provisioning operations. This is a known SAP-side rate limiting issue. Contact SAP support for assistance.

Note

For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.

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.