Skip to main content
Question

Can we hard-code the timeout period on a Token Service web connection?


We are using a custom Token Based web connection to an external service. The service does not return an expiry time - it is always 180 minutes.

 

Is there a way to hard code an expiry duration on a token retrieved by the web connection? The UI for defining a Token Based web connection seems to only support an expiry time being returned by the token service.

2 replies

caracadrian
Contributor
Forum|alt.badge.img+23
  • Contributor
  • November 3, 2021

It depends on the service.

Can you provide a return example from a browser Developer Tools so we can see the Headers and the Response?


  • Author
  • November 3, 2021
caracadrian wrote:

It depends on the service.

Can you provide a return example from a browser Developer Tools so we can see the Headers and the Response?

The response body is JSON:

{
    "success": true,
    "message": "Logged In",
    "data": {
        "token": "dc..redacted...aebea8b0192661"
    }
}

There is a Date header in the response, which is the current time (of the web server).  No other notable response headers (just standard ones like content length, content type).


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings