Caching in AJO

[NeeharikaSh]

Hey all,

We are using a custom action in a journey, which hits a proxy api to generate a token and inject it as an authentication header for subsequent calls. We are setting the cacheDuration in the authentication payload to 1 hour so that the token in response gets stored in the cache and it is good for an hour for the next call to the API. Is there any way that we can test the caching or the fact that the token generated is being used for the next calls for an hour and then a new token is generated?

[SatheeskannaK]

@NeeharikaSh, I would suggest trying this approach in Postman and testing it out.

[NeeharikaSh]

Is there any way we can check the same in the AJO Platform itself?

[SatheeskannaK]

No. I don't think so. 

[dugganab · Accepted solution]

Not on the AJO side, this needs to be monitored on the customer side to understand how frequently the authentication end point is being hit.

[NeeharikaSh]

Could you help me with how that can be done?

[dugganab]

I believe customer should be having a monitoring tool (say, for ex:- Prometheus / Grafana / Datadog etc.,) which their IT team should help assist with.