User Defined (OAuth): Lifetime of access_token

[Nikolay_Podnebesnyi]

We use Web Service Data Actions with User Defined (OAuth) credential type. We do configuration like it describes here: How to use the User Defined (OAuth) credential type. For example the integration name is "Bsv_Test"

1. Such integration creates Data Action with "Custom Auth" type with name "Bsv_Test (Auth)". The response from this Data Action is:
   
   
2. We create custom action and use auth response in request. For example with name "BDS_Test"
3. In "Architect" we create "Inbound Email" flow with name "Bsv_Test_Flow". We add "Call Data Action" to the "Start" and set "Category": Bsv_Test, "Data Action": BDS_Test.
4. Save and Publish flow.
5. Then we call this Flow using ConversationsApi.PostConversationsEmails method from library PureCloudPlatform.Client.V2
6. Our expectation is that the "access_token" from the "Bsv_Test (Auth)" will be used no more than the set interval in the "expires_in" property. According to documentation RFC 6749: The OAuth 2.0 Authorization Framework It's lifetime in seconds of the access token, but in fact your service continues to use the token for about an hour. We set expires_in: 900, we expect that after 15 min when we call "Bsv_Test_Flow" the new request for "access_token" will be received but in fact it doesn't. What did we do wrong or how can we set the lifetime of the "access_token" so that you do not continue to use it after it has expired?

[Jason_Mathison]

Hi Nikolay,

Is the behavior you are experiencing causing you an issue? Our expectation is that if we attempt to use an expired token the request would get an authentication error. At that point we would update our cache with a new authentication token and try the request again.

--Jason

[Nikolay_Podnebesnyi]

HI Jason,

We checked. We don't have any problems