question

Sameer Roy avatar image
Sameer Roy asked Anirban Sen Chowdhary edited

What is the lifespan of tokens ffrom ringcentral oauth server

I am getting both access_token and refresh_token for oauth call.

Is there any documented life span for both the tokens generated?

What is the longevity of access_token and refresh_token? Can this be configurable?

Is there some way I configure the oauth call not to generate refresh_token? I have seen in other oauth servers that we can only get access_token and avoid refresh_token being generated.

How can I do here?

oauth2token
1 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

·
Anirban Sen Chowdhary avatar image
Anirban Sen Chowdhary answered Anirban Sen Chowdhary edited

Let's answer one by one.

Is there any documented life span for both the tokens generated?

What is the longevity of access_token and refresh_token?

Access token lifetime is 3600s = 1 hour

Refresh token lifetime is 7 days(1 week)

you can refer: https://forums.developers.ringcentral.com/articles/1426/generating-access-token-and-refresh-token-and-effi.html

Can this be configurable?

I don't think so

Is there some way I configure the oauth call not to generate refresh_token?

Yes, you can. Just use refresh_token_ttl=0 in the OAuth request along with your other parameters like grant_type, extension etc.

You will not display refresh_token as it will expire before it display in response and you can skip that in your API response.

1 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.