schattopadhy
January 18, 2026, 3:26pm
1
Hi All,
We have an application which supports SCIM but does not have any soft delete API.The user automatically gets deleted when you trigger disable operation from sailpoint.
However the issue is after deleting it again tries to fetch the user as per the logs and since the user is deleted there is no response and it gives us 404 error .
IS there any way to stop the single account aggregation after the disable operation in SCIM SAAS connector?
amulpuru
January 18, 2026, 7:08pm
2
Hi @schattopadhy ,
It seems like adding NO_RANDOM_ACCESS feature string to your connector solves your problem of disabling single account aggregation after an operation try this one
Reference
We have 2 (non-compliant) SCIM sources that do not return inactive users either through full aggregations or single user aggregations. This works fine because we do not care about the disabled users on these sources, however, it does present a problem when we try to disable an account on termination. The disable operation works as expected and disables the user on the source, but SailPoint immediately tries to the GET the user record again and that fails, which makes it appear that the disable f…
Documentation
Thanks in advance
schattopadhy
January 19, 2026, 9:11am
3
schattopadhy:
Hi All,
We have an application which supports SCIM but does not have any soft delete API.The user automatically gets deleted when you trigger disable operation from sailpoint.
However the issue is after deleting it again tries to fetch the user as per the logs and since the user is deleted there is no response and it gives us 404 error .
IS there any way to stop the single account aggregation after the disable operation in SCIM SAAS connector?
@amulpuru i tried but it still throws an error but deletes the user in target application
msingh900
January 19, 2026, 11:18am
4
@schattopadhy
As per the documentation,
NO_RANDOM_ACCESS: The source does not support random access and the getObject() methods should not be called and expected to perform.
using this it would not call the getObject method and single aggregation wont be performed.
Did you checked that if the full aggregation is trying to find the user or single account aggregation.
schattopadhy
January 19, 2026, 3:11pm
5
@msingh900
The aggregation is getting triggered after the disable operation is being performed
msingh900
January 19, 2026, 3:23pm
6
Have you added NO_RANDOM_ACCESS?
amulpuru
January 19, 2026, 5:28pm
7
Can you please confirm that you have added NO_RANDOM_ACCESS to featurestring list for the connector as per doc and other reference I see it working
schattopadhy
January 29, 2026, 11:22am
8
yes but in my case it does not work