Caching in AJO

Forum|Forum|1 year ago
February 16, 2024
2 replies
1269 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Mohan_Dugganab

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.

SatheeskannaK

Community Advisor

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

Thanks, Sathees

N

NeeharikaShAuthor

Level 2

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

SatheeskannaK

Community Advisor

No. I don't think so.

Thanks, Sathees

Mohan_Dugganab

Accepted solution

Adobe Employee

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.

N

NeeharikaShAuthor

Level 2

Could you help me with how that can be done?

Mohan_Dugganab

Adobe Employee

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

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded