Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

SAV4SAV Access Import

Alex_Terry
Regular Contributor
Regular Contributor

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:

Alex_Terry_0-1715329625173.png

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:

Alex_Terry_1-1715329705643.pngAlex_Terry_2-1715329722795.png

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?

12 REPLIES 12

Raghu
Honored Contributor
Honored Contributor

@Alex_Terry  Connector level Config Json below things declare and chekc

 

Raghu_0-1715330666833.png

 

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


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

Alex_Terry
Regular Contributor
Regular Contributor

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

Raghu
Honored Contributor
Honored Contributor

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


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

naveenss
All-Star
All-Star

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

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Alex_Terry
Regular Contributor
Regular Contributor

Hi @naveenss 

See attached logs and JSON.

Restart the server and validate 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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

Provide connection and job configs screenshot


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Alex_Terry
Regular Contributor
Regular Contributor

Job Config:

Alex_Terry_0-1715676221874.png

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. 

 

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

Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

  • 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?

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


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.