Apigee NG requires that the cache entry has an expiry time for a cache resource

[davidmitchell2019]

Apigee NG requires that the cache entry has an expiry time for a cache resource.
When the shared flow does a lookup on the cache entry it exists, but when the set am header policy tries to add the bearer token it cant find the entry

[davidmitchell2019]

cache access token policy below

[davidmitchell2019]

<PopulateCache name="PCCacheAccessToken"> <CacheKey> <Prefix>gcp.sa</Prefix> <KeyFragment ref="private.gcp.service_account.client_id"/> <KeyFragment ref="token.purpose"/> </CacheKey> <CacheResource>gcp-tokens</CacheResource> <Source>private.gcp.access_token</Source> <ExpirySettings> <TimeoutInSec>600</TimeoutInSec> </ExpirySettings> </PopulateCache>

[davidmitchell2019]

[davidmitchell2019]

So the lookup still finds the entry even tho the entry has expired

[tyayers]

Maybe an issue with TimeoutInSec, which is deprecated? Try TimeoutInSeconds, haven't tested it yet but could be the problem..

[davidmitchell2019]

Syntax error on my behalf, have a great day :-)

[danistrebel]

Thanks for reporting this. I can confirm the requirement for the ExpirySettings entry.

I am a bit worried because the validation only allows for the deprecated TimeoutInSec instead of TimeoutInSeconds. I'll look into this and make some adjustment to the sharedflow based on that.