SAV4SAV Access Import

[Alex_Terry]

Hello, 

We have onboarded Saviynt into our instance through the SAV4SAV connection. We have scheduled both account and access imports. When the account import is ran it imports the correct records and returns a success status and is populated with an end date time, see below:

However when we run the access import it returns a successful status message but isn't populated with an end date in the record, see below:

We have confirmed that the import job is running by creating a new SAV_ROLE and then running an access import. When we did this we were able to verify that this role was imported correctly into the entitlements for this endpoint.

Can you help us resolve this issue so that the job record is populated with an end date and time?

[Raghu]

@Alex_Terry  Connector level Config Json below things declare and chekc

{"show logs": "true"},{"connectionTimeoutConfig":{"connectionTimeout":20,"readTimeout":50,"r etryWait":2,"retryCount":3}}

[Alex_Terry]

Hi @Raghu I've implemented this and tried running the jobs again with the same results.

[Raghu]

@Alex_Terry  We also earlier same issue faced, but saviynt team applyed those changes. now we not yet see any blank end date

[naveenss]

Hi @Alex_Terry Do you see any error in logs? Also can you please share the JSON used for this access import?

[Alex_Terry]

Hi @naveenss 

See attached logs and JSON.

[rushikeshvartak]

Restart the server and validate 

[Alex_Terry]

I've performed an application restart and we're still seeing the same result.

[rushikeshvartak]

Provide connection and job configs screenshot

[Alex_Terry]

Job Config:

For the connection config we used the default ConnectionJSON. The ImportAccountEntJSON is attached in a previous reply. I can provide the other populated fields however they are what was provided as the default. 

[rushikeshvartak]

• connectionTimeoutConfig should have resolved this issue.
• Does it have issue with all REST Connector ? if no compare configs

[Alex_Terry]

• ConnectionTimeOutConfig: I've tried running the job both with this config and without with no difference to the end result.
• This isn't an issue we've seen with other REST connectors. Looking at the configs for both of the different connections I can't see a significant difference that would cause this issue in the importAccountEntJSON between the two connections

Could you provide us with additional troubleshooting steps that we can take?

[rushikeshvartak]

It seems connection created through global configuration making issue. If its specific application please raise support ticket