NERM getProfiles API , returns HTTP 400 whenever no profiles exists

[sakthikumar2596 (Sakthikumar Ganesan)]

Which IIQ version are you inquiring about?

8.5

Please share any images or screenshots, if relevant.

Configured Delta aggregation in WS connector in IIQ for fetching profiles from NERM, based on last successful aggregation timestamp from Application XML.

getProfiles API returns HTTP 400 whenever no profiles exists under the timeframe ( if no updates found on profiles from NERM end).

However, in SailPoint IIQ end:

HTTP 400 is treated as a hard failure, which causes the WS operation and aggregation/account fetch to fail, even though “no profiles found” is actually a valid business condition (not an error).

trying to handle in WS AfterRule by adding 400 as success code, but still facing issue with attribute path.

Please provide insights to handle this 400 NERM bad request in IIQ.

Thanks,

Sakthi

[joshua_morris]

As of today, this is working “as designed” and how it has worked all along. We agree that a 200 response would be more appropriate in these scenarios, but at this point this API as worked this way since day 1 and modifying this would present a breaking change for all of the existing customers already using this API today. We plan to make this improvement as part of the next generation of APIs for this service, but we do not plan to alter the current API at this time.