Non-Compliant Settings

Feedback Documentation Feedback Connectivity Documentation Feedback
1

The SCIM 2.0 source supports the configuration of a non-compliant SCIM server. In the SCIM 2.0 source UI, on the Relax Configuration sub-panel, enable the Non Compliant Server? option to skip SCIM 2.0 validation for each response from this server. Use this if your SCIM 2.0 Server is not fully compliant with SCIM 2.0 specifications.

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/scim_2_0/help/integrating_scim2/noncompliant_settings.html
2

Hello,

We discovered that the SCIM payload coming from the server we’re trying to connect doesn’t comply with the RFC specs. In particular, the Resources array comes with its label in all lower cases (i.e. “resources”).

The docs cover this very case by stating:

You can configure a custom rootPath for aggregating Accounts if the rootPath of /Users does not comply with SCIM RFC. For example, if /Users rootPath is “resources” instead of the SCIM RFC standard “Resources", use the Update Source (Partial) API as shown below in the JSON Payload example:
[{“op”: “add”,“path”: “/attributes/aggregation_rootPath”,“value”: “$.resources[*]”}]

We’ll, I tried to configure rootPath following the advice, but I got the following error:

{
    "detailCode": "400.1 Bad request content",
    "trackingId": "10c8050759d14ad19ca585b384c2b377",
    "messages": [
        {
            "locale": "und",
            "localeOrigin": "REQUEST",
            "text": "The request was syntactically correct but its content is semantically invalid."
        },
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "The request was syntactically correct but its content is semantically invalid."
        }
    ],
    "causes": []
}

I also tried to use:

[
  {
        "op": "add",
        "path": "/connectorAttributes/aggregation_rootPath",
        "value": "$.resources[*]"
  }
]

Which successfully inserts the node under connectorAttributes, but it does NOT help to aggregate the missing resources (Users nor Groups).

UPDATE:
I tried again the /connectorAttributes/aggregation_rootPath with fresh JSONPath and it worked!

We’re good to continue integrating our source, but I’m leaving this thread here as the documentation is still wrong and needs to be updated.

Thanks!

@colin_mckibben, can you loop someone from SailPoint’s documentation team to look into this?

Thank you!

Elisa.

1 Like
4

Hi Elisa,

Thanks for looping in the documentation team for this. I have created CONDOCS-6720 to track the progress to update the docs based on your feedback. We’ll update you here once the change has been implemented.

-Josh

1 Like
5

Thanks @joshb488!
Since I confirmed the proper path for the PATCH call, I guess it’s an easy change but let me know if you need anything!
Have a good day.
Elisa.