SCIM 2 Connector Unable To Discover Attributes

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

I’m getting the below error on a scim connector that was working a month ago. It is for KnowBe4 and the vendor doesn’t support Sailpoint/Knowbe4 but we’ve used scim 2 to get data/provision anyways.

  • Unable to discover the [account] schema for this application.[sailpoint.connector.ConnectorException: openconnector.ConnectorException: Invalid boolean value: null of type: java.lang.String]
2

If you have access to the application creds try validating the connection directly. And also check the logs by enabling the below traces in IIQ

# logger.spScimCommon.name=sailpoint.scim.common
# logger.spScimCommon.level=all

# logger.openconnectorScim2.name=openconnector.connector.scim2
# logger.openconnectorScim2.level=all

# logger.SCIM2.name=openconnector.connector.scim2.SCIM2Connector
# logger.SCIM2.level=trace

# logger.openconnectorRest.name=openconnector.rest
# logger.openconnectorRest.level=all

# logger.SCIMLWR2.name=sailpoint.rest.scim.LaunchedWorkflowListResource
# logger.SCIMLWR2.level=trace
 
# logger.SCIM2REST.name=openconnector.connector.scim2.SCIM2RestApi
# logger.SCIM2REST.level=trace

Make sure to enable them before capturing and disable them once capture

3

I’m able to use postman to get users. I get the below right before the logs spam the error:

Line 23548: 2025-10-16 08:53:22 TRACE JSONReader:97 - Entering buildSimpleValueFromSchemaAttribute:

Arguments => null, {name=name, description=The components of the user’s real name. Providers MAY return just the full name as a single string in the formatted sub-attribute,

or they MAY return just the individual component attributes using the other sub-attributes, or they MAY return both. If both variants are returned,

they SHOULD be describing the same name, with the formatted name indicating how the component attributes should be combined.,

type=complex, multiValued=false, required=false}, {uniqueness=none, name=caseExact, description=Indicates if a string attribute is case-sensitive.,

mutability=readOnly, type=boolean, multiValued=false, caseExact=false, returned=default, required=false}

Line 23549: 2025-10-16 08:53:22 TRACE JSONReader:97 - Entering coerceObject:

Arguments => null, {uniqueness=none, name=caseExact, description=Indicates if a string attribute is case-sensitive., mutability=readOnly, type=boolean, multiValued=false, caseExact=false, returned=default, required=false}

Line 23550: 2025-10-16 08:53:22 DEBUG SCIMTypeConverter:39 - coercing value: null for attribute: caseExact of type: boolean
4

Have you enabled Non-compliant Server? The error indicates that IIQ is not getting a valid schema definition from the server.

5

That was it. That’s super odd because it was working 2 months ago without it.

6

Could be a problem with the Source /schemas endpoint?

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.