IIQ 8.x
I was able to add a custom object type in the SCIM connector via debug and discover it successfully.
But when I try to aggregate it or do a preview, it throws 404 resource not found because I think it is calculating incorrect URL.
Any idea why is it adding the URL twice?
openconnector.connector.scim2.SCIM2Connector:3025 - Aggregation URL: https://api.scim.dev/scim/v2/https://api.scim.dev/scim/v2/Offices?startIndex=1&count=50
please provide screenshot of your configuration.
Thanks Manish for your response.
Log:
Resource Type: Office
SCIM 2.0 SSL protocol version used is null
SCIM 2.0 URL used is https://api.scim.dev/scim/v2
Resource Type: Office
openconnector.connector.scim2.SCIM2Connector:3025 - Aggregation URL: https://api.scim.dev/scim/v2/https://api.scim.dev/scim/v2/Offices?startIndex=1&count=50
Hi @cinilsunny , can you please check whether the license is active for this source? If it is a free source, please share the correct URL. When I try to open it, I receive an “invalid token” error.
Can you please give correct URL.
Hi @cinilsunny
I followed your steps up to the Preview stage, but I hit a roadblock. Since the free account expires after 119 minutes, I couldn’t test the complete scenario. If you have a paid account, please share the details so I can finish testing.
I was able to replicate the issue and am currently analyzing it. It appears to be a problem with the custom API or limitation of SCIM 2.0 connector.
Test Successful
account Preview successful
Discover Schema Attributes successful
But for Object Type: Office - Preview: Failed/Error
{
"totalResults": 5,
"itemsPerPage": 5,
"startIndex": 1,
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:ListResponse"
],
"Resources": [
{
"schemas": [
"dev:scim:Office"
],
"id": "a0e03fd1-7e94-4a2d-934d-035543059b2a",
"meta": {
"created": "2026-01-19T19:13:58+00:00",
"lastModified": "2026-01-19T19:13:58+00:00",
"location": "https://api.scim.dev/scim/v2/Offices/a0e03fd1-7e94-4a2d-934d-035543059b2a",
"resourceType": "Office",
"version": "W/\"187da77f91f422152ecc21ef055166b1dbba9163\""
},
"name": "New York Office",
"employees": []
},
{
"schemas": [
"dev:scim:Office"
],
"id": "a0e04361-3b8e-4bbb-9ea2-830fd589abf9",
"meta": {
"created": "2026-01-19T19:23:55+00:00",
"lastModified": "2026-01-19T19:23:55+00:00",
"location": "https://api.scim.dev/scim/v2/Offices/a0e04361-3b8e-4bbb-9ea2-830fd589abf9",
"resourceType": "Office",
"version": "W/\"adf13fa12d6ce8bffb730e2a79145c5645ec3d63\""
},
"name": "test-user",
"employees": []
},
{
"schemas": [
"dev:scim:Office"
],
"id": "a0e04385-432d-4490-8710-9ca7873cc52c",
"meta": {
"created": "2026-01-19T19:24:19+00:00",
"lastModified": "2026-01-19T19:24:19+00:00",
"location": "https://api.scim.dev/scim/v2/Offices/a0e04385-432d-4490-8710-9ca7873cc52c",
"resourceType": "Office",
"version": "W/\"742f22532703cb2b6b296156e294f4c38a851f48\""
},
"name": "dev-user",
"employees": []
},
{
"schemas": [
"dev:scim:Office"
],
"id": "a0e04394-8bb6-4609-aa87-b97d56bc9528",
"meta": {
"created": "2026-01-19T19:24:29+00:00",
"lastModified": "2026-01-19T19:24:29+00:00",
"location": "https://api.scim.dev/scim/v2/Offices/a0e04394-8bb6-4609-aa87-b97d56bc9528",
"resourceType": "Office",
"version": "W/\"ee67af7bd8c2783d8cf47d1f43eba3fd00aa18fe\""
},
"name": "qa-user",
"employees": []
},
{
"schemas": [
"dev:scim:Office"
],
"id": "a0e0439e-268f-4ae5-8e1c-69b5d95ffe5a",
"meta": {
"created": "2026-01-19T19:24:35+00:00",
"lastModified": "2026-01-19T19:24:35+00:00",
"location": "https://api.scim.dev/scim/v2/Offices/a0e0439e-268f-4ae5-8e1c-69b5d95ffe5a",
"resourceType": "Office",
"version": "W/\"121e33c82e6d88270c50f9f327f0c7652afe41a1\""
},
"name": "prod-user",
"employees": []
}
]
}
If my understanding is correct the SCIM 2.0 connector will not support the custom object type other than the below default objectType:
nativeObjectType=“User” objectType=“account”
nativeObjectType=“Group” objectType=“group”
nativeObjectType=“Entitlement” objectType=“entitlements”
nativeObjectType=“Role” objectType=“roles”
I have tested with Group schema as well; it is working fine:
let me refer the Official SailPoint IIQ SCIM 2.0 documents to see what is mentioned over there.
As per SailPoint Official Connector document: Schema Attributes it will support following 4 object types.
Other than this the Custom object type: Office is not a standard schema type.
“schemas”: [
“dev:scim:Office”
],
The standard schema example:
"schemas":
["urn:ietf:params:scim:schemas:core:2.0:User",
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"],
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:Group"],
reference document link: RFC 7643 - System for Cross-domain Identity Management: Core Schema
Yeah, just create a new free token in https://scim.dev/
Thanks Pattabhi..check SCIM 2.0 Relax Configuration, it does support custom object type and that is the reason discover schema works.
I guess then there is no way to modify the outgoing URL as that URl is somehow fetched from the endpoint so maybe the endpoint is not storing it in the correct format.
If we are able to remove the base URL then all is good or just add the context URL to the base URL.
Log:
Resource Type: Office
SCIM 2.0 SSL protocol version used is null
SCIM 2.0 URL used is https://api.scim.dev/scim/v2
Resource Type: Office
openconnector.connector.scim2.SCIM2Connector:3025 - Aggregation URL: https://api.scim.dev/scim/v2/https://api.scim.dev/scim/v2/Offices?startIndex=1&count=50
@cinilsunny
is it possible to update the above schemas value from dev:scim:Office to urn:ietf:params:scim:schemas:core:2.0:Office ?
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:Office"
],
No Pattabhi..maybe they will allow if we pay for the subscription..anyways, I guess it is not possible to modify the outgoing aggregation URL or maybe the engineering team will know.
Yes, earlier it was a free source and was available for all operations for three months.
@cinilsunny Have you thought of using webservices connector instead of a SCIM connector? You can extend it to use custom endpoints based on your use cases as well.
Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(
, 
, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
Yes, that is always an option but just trying to see how to make it work using SCIM