Need to know about caching of the token generated by DataAction of type Custom Auth

Data Actions
1

Hi All,

We have a set up like below

1.We created a Integration of type User Defined (OAuth) and passing the url , clientId and clientsecrete details and url is inhouse API(Not using any of the genesys provided API) and this is the API which gives us the token to invoke the other API (inhouse API)

2.Once we created Integration of type User Defined (OAuth) it will automatically created a DataAction of type (Custom Auth) and the output of this provide the details of token and token expiry details which are redacted.

3.We created another DataAction of type custom under the same integration and passing the access token generated by DataAction of type Custom Auth and we got good result and integrated the same with Architect call flow.

4.When ever DataAction of type custom is invoked in the Architect call flow it implicitly invoke the DataAction of type (Custom Auth) since it is under the same integration and provide the access token and this access token is used by DataAction of type custom to invoke the API

For each call the above process repeats.

Our question is DataAction of type (Custom Auth) where we are getting access token , is this access token is cached implicitly or will it be going to create a new access token for each call (it's token generated by in house Kong API token and not using any of the genesys related API), can someone please help with this as we are unable to check form our end since access token is redacted and unable figure it out whether it's using new token or reuse the existing token.

We even raised case with genesys (0003594253) genesys recommends to put this query in this forum.

Any help will be really appreciated.

Thanks in advance !

Thanks,
Sandesh N.

2

The data action service will create a limited number of auth tokens and reuse them for a while. For a busy data action you can expect the requests that require a new auth token to be well under 1%.

The implementation of this is not publicly documented so my answer has to be vague, but the overall answer is that we do cache the auth requests.

--Jason

3

Hi Jason,

Thanks a lot for your update and really appreciate it.

Need some clarification regarding this.

The data action service will create a limited number of auth tokens -->We are using our inbuilt API URL in the data action of type Custom Auth to generate token , so does this token will also get cached ?

URL we are using to generate token is https://tokenServer?scope=123 and we are trying to understand, token generated by this will be going to cache or not when we used in data action of type Custom Auth , could you please help.

Thanks,
Sandesh N.

4

Tokens created by custom auth actions are cached. The exact number of tokens that are created and cached will vary on several factors, but in general for a busy integration only a very small percentage of requests will create a new auth token.

5

Thanks a lot Jason !

Your inputs are really helpful

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.