Getting NullResponseFromTarget during user import using REST connector

[ganimkt]

Hello Team,

I have successfully integrated the Oracle HCM application using REST connector. 

Authentincation : Basic Aunthentication 

Total Users : 32000

User import job run time for 12000 users : 42 minutes ( approximately )

When I ran the user import job it's failing after updating for 12000 users with the error "NullResponseFromTarget". I am assuming that this error is caused due to expired aunthentication. 

Can anyone confirm does saviynt do re-authentication on regualar intervals during the import. 

When I ran the job only for last 8000 with the help of limit and offset parameters it didm't returend "NullResponseFromTarget" error, due to this I am assuming that re-authenication isn't happening from saviynt side.

Please suggest on this.

[NM]

Hi @ganimkt , for basic authentication we use username and password how is that getting expired?

[ganimkt]

Hi @NM , Yes you are correct, But there will be a session for every time we authenticate, I am assuming that the session is being expired. Not sure how to check the session timing. For example if you login into saviynt instance and if you are ideal for couple of minutes then the session will get expired and you will be forced to log off.

[rushikeshvartak]

Check with Oracle HCM documentation on session expiry

[ganimkt]

This is what I found in internet 

But could you please tell me does saviynt re authenticate if the session got expired ?

[rushikeshvartak]

Share connection JSON & also confirm if configJSON is configured 

[ganimkt]

In the configJson, I have put only showlogs: true, Below is the connctionJson.

{
"authentications": {
"userAuth": {
"authType": "basic",
"errorPath": "error.code",
"maxRefreshTryCount": 5,
"tokenResponsePath": "access_token",
"properties": {
"userName": "XXXXXX",
"password": "XXXXX"
},
"authError": [
"InvalidAuthenticationToken",
"AuthenticationFailed"
],
"retryFailureStatusCode": []
}
}
}

[rushikeshvartak]

use below configJSON

{
  "showLogs": false,
  "connectionTimeoutConfig": {
    "connectionTimeout": 10,
    "readTimeout": 60,
    "writeTimeout": 60,
    "retryWait": 2,
    "retryCount": 3
  }
}

Use below Connection JSON

{
    "authentications": {
        "userAuth": {
            "authType": "Basic",
            "httpMethod": "POST",
            "url": "https://your_oracle_hcm_url_here",
            "httpContentType": "application/json",
            "httpHeaders": {
                "Accept": "application/json",
                "Content-Type": "application/json"
            },
            "properties": {
                "userName": "XXXXXX",
                "password": "XXXXX"
            },
            "tokenType": "Bearer",
            "tokenResponsePath": "access_token",
            "authError": [
                "InvalidAuthenticationToken",
                "AuthenticationFailed"
            ],
            "expiryError": [
                "TokenExpiredError"
            ],
            "errorPath": "error.code",
            "retryFailureStatusCode": [401, 403],
            "timeOutError": ["TimeoutException"],
            "maxRefreshTryCount": 5
        }
    }
}

[rushikeshvartak]

•  verify the validity of a token or specific session, check its configuration.

[ganimkt]

Can you please elaborate how can I check valididty of a session. 

[Dhruv_S]

Hi @ganimkt 

nullresponsefromtarget doesnot necessary imply that the session expired in between the import. Hence, we require full logs when this import was run along with start and end timings of the job.

When a token expires, REST connector retries for the fresh token based on the retryfailurestatus code which is usually 401 in the case of authentication failure.

In case of basic authentication, session expiry should be dependent on the target application.

I would suggest you open a ticket with full logs and job details, we will check and let you know. Based on the analysis of logs, we can suggest you further.

Regards,

Dhruv Sharma

[Dhruv_S]

Hi @ganimkt 

Please confirm if a ticket has been opened already. Else I can open a ticket on your behalf and complete logs can be shared on that.

Regards,

Dhruv Sharma