Access_token is not getting refresh automatically

Hi,

I have downloaded the new FDK version for OAuth fixes, but still, access_token is not getting automatically refreshed after access_token is expired

OAuth_config file :

{
    "client_id": "<%= oauth_iparams.client_id %>",
    "client_secret": "<%= oauth_iparams.client_secret %>",
    "authorize_url": "https://app.domain.com/authorize-app/<%= oauth_iparams.client_id %>",
    "token_url": "https://api.domain.com/api/integrations/oauth/token",
    "token_type": "account",
    "options": {
        "scope": "offline_access"
    },
    "oauth_iparams": {
        "client_id": {
            "display_name": "Client ID",
            "description": "Please enter your  client ID",
            "type": "text",
            "required": true
        },
        "client_secret": {
            "display_name": "Client Secret",
            "description": "Please enter your client secret",
            "type": "text",
            "secure": true,
            "required": true
        }
    }
}

I can see access_token and refresh_token in my local store of app
Can anyone explain about when freshservice will refresh the access_token?

Is there any other condition required to be satisfied for refreshing the access_token?

Thanks!!

We recently released a fix that addressed similar other issues. Can you please try to re-authorize? After that, the refresh should happen properly. If it still doesn’t, please let us know.

Hi @kaustavdm,

I have updated the FDK version
I have re-authorize the app also but it is not getting refreshed
It remains the same access_token

In our third-party authorization, they are sending 400 status code when the token is expired

Is there any other condition required to be satisfied for refreshing the access_token?

Thanks !!

Any update on the above use case ? @kaustavdm

Anyone can help!!

Apologies for the delay, @Anushka_Ahir.

I have asked the engineering team to look into this.

@Anushka_Ahir I have learnt that the dev platform currently supports access_token refresh only for endpoints that return HTTP 401. Is there any chance you can ask the 3rd party API to change the return code?

No @kaustavdm , the Third party will not change the return code

Is there any chance to change this validation from freshService side?

Thanks !!

This is handled at the developer platform level. I have requested the @Developer-Platform team to let me know if it will be possible to support HTTP status 400 for OAuth token refresh. I’ll let you know once I hear from the team.