Closed MalibuKoKo closed 5 months ago
cc @mattklein123
I'll pick this one up
@MalibuKoKo We retrieve this from STS using json format which does in fact use the unix timestamp. However STS is returning a scientific notation version in the json payload. I'm investigating with the STS team as to whether this is accurate and then can propose a fix.
It's not expected behaviour from STS, but valid json nontheless. I have a fix for this that will go to PR shortly.
PR https://github.com/envoyproxy/envoy/pull/34426 fixes this issue. Apologies for the delay, the fix was dependent on https://github.com/envoyproxy/envoy/pull/34138 merged today
@nbaws: thank you very much for the correction I will test the fix in the next version.
A warning explain than Expiration value is missing or not an integer. I think it's a misunderstood about Expiration field, we can see an example on API documentation. Timestamps are formatted according to the ISO 8601 standard.
You can find the impacted code here, and could be patched quickly with the same logic we can found here
Patch
Repro steps:
Manifest
Logs: