Unable to parse the date startdate from the payload: 2020-11-30 00:00:00"

 End date extension for the record via TDI API call fails in the new Saviynt 2023 development environment. Similar case in earlier version 5.5 was successfull 

Case- We were setting the enddate for the users via postman. While we were hititng APIs to set enddates, we were getting response from saviynt 2023 in different date format like yyyy.mm.dd. Due to that, it was becoming barrier for us because all consumbers were consuming the API in date format MMDDYYY

Earlier in V5.5, date format in response was mm.dd.yyyy and the same response every API consumbers were using and consuming for their applications. 

Fixed:

This is because the getUser call was giving a response which was a non-standardised one in 5.5SP5 "06/08/2020T10:35:46+0000".

Now in EIC Version 2023, the getUser API call gives a response, where all the dates are returend in the date format "2023-03-29 12:27:47" 

This is fixed by a configuration WS_RESPONSE_DATE_FORMAT_AS_DB in Saviynt Version 2023.

message "invalid connectionconfig format" in postman with Saviynt v23.5

Issue: In Saviynt version 2023, we have noticed a problem. API call works fine when we use Postman to call the /getEndpoints API with the values "offset": 0 and "max": 370.

However, if we go above the maximum value of 370, say 371 and so on. The API call is failing in that situation with the error "Invalid connection configuration format."

Actually, we have API data flows from ServiceNow to TDI --> Mulesoft (as a proxy)--> Saviynt . We noticed this problem when we tested the API calls from TDI to Saviynt . Below error showed up in the logs each time when we attempted to call Saviynt's get endpoints using API from TDI. 

SaviyntConnector.prototype.findEndpoints: Error returned in response payload. Code: 1, msg: Invalid connectionconfig format, payload: {"errorCode":"1","message":"Invalid connectionconfig format","statusCode":"412"}{"errorCode":"1","message":"Invalid connectionconfig format","statusCode":"412"}{"errorCode":"1","message":"Invalid connectionconfig format","statusCode":"412"}{"errorCode":"1","message":"Invalid connectionconfig format","statusCode":"412"}'

Solution: It was data issue in the endpoint connection config. After fixing that, it has was resolved.