SSO Integration: Oauth authorization token expires too quickly and causing scheduled jobs to fail. Does not appear to be using the refresh token to stay alive.

[Community Alums]

SAM issue: OKTA SSO Integration: Oauth authorization token expires too quickly (30mins) and causes scheduled jobs to fail before they can be completed. Does not appear to be using the refresh token to stay alive. Any advice, or should this go to HI Support?

[Raghu Ram Y]

Hi,

By OOB, the instance issues access tokens will have 30-minute lifespan, so you need to generate a new access token before it expires.

[Community Alums]

Hi Raghu,

Thank you for your response. How can I go about generating a new access token before it expires?

[Raghu Ram Y]

Create a schedule job and generate the new access token by using refresh token..

and also you can increase lifespan of Access Token, to increase it just navigate to "System Oauth -> Manage Tokens"

Open your access token record and update the Expire date, so that Access token won't expire for every 30 mins..

[Community Alums]

Hi Raghu,

Can you help me with the scheduled job idea?

I did try increasing the lifespan of the access token directly, and it doesn't work in this case. I increased it quite a bit too. 

The access token record expiration field appears to get auto set for 1hr.

I believe if I request a new token, this field will be overwritten whenever I need to do that, and so, I'd need to keep updating this field. I don't believe we want to keep it open indefinitely.