You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are observing an increase in the receiving of expired JWT tokens in the
archive callback service since Feb 5th afternoon UTC.
Our logs show that users are being directed to the Kinetiq player at the
time when the token was issued (iat below), which is the beginning of the
24-hour window till the JWT expires.
However, we are receiving the callback after 24 hours after the token has
already expired.
Error log for reference in case this helps investigate:
(claims->{"documentId":"Fmv5M5EL4uYnUdrekq1_heqDTEU","userId":"647774ab10dcb80008f1f1cb","companyId":"581c85feb3798a22aca7521d","productType":"kinetiq-archiving","exp":1738849104,"iat":1738762704})
rejected due to invalid claims or other invalid content. Additional
details: [[1] The JWT is no longer valid - the evaluation time
NumericDate{1738876792 -> Feb 6, 2025, 9:19:52 PM UTC} is on or after the
Expiration Time (exp=NumericDate{1738849104 -> Feb 6, 2025, 1:38:24 PM
UTC}) claim value.]*
Can you please look into this and let us know if there is a delay at your
end?
Thanks,
Naji
NAJI ADNAN
Engineering Team Lead, Meltwater Berlin
The information contained in this email may be confidential. It has been sent for the sole use of the intended recipient(s). If the reader of this email is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the message.
For more information on how we process personal data please see www.meltwater.com/privacy. Please note that neither the Company nor the sender accepts any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments.
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
The text was updated successfully, but these errors were encountered:
Issue Creater Email: Naji Adnan [email protected]
Email Body:
Hi team,
We are observing an increase in the receiving of expired JWT tokens in the
archive callback service since Feb 5th afternoon UTC.
Our logs show that users are being directed to the Kinetiq player at the
time when the token was issued (iat below), which is the beginning of the
24-hour window till the JWT expires.
However, we are receiving the callback after 24 hours after the token has
already expired.
Error log for reference in case this helps investigate:
*Caused by: org.jose4j.jwt.consumer.InvalidJwtException: JWT
Can you please look into this and let us know if there is a delay at your
end?
Thanks,
Naji
NAJI ADNAN
Engineering Team Lead, Meltwater Berlin
[email protected] | www.meltwater.com
LinkedIn http://de.linkedin.com/pub/naji-adnan/8a/a44/38b | twitter
https://twitter.com/najAdnan
Meltwater – Your friends on the outside.
--
Disclaimer
The information contained in this email may be confidential. It has been sent for the sole use of the intended recipient(s). If the reader of this email is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the message.
For more information on how we process personal data please see www.meltwater.com/privacy. Please note that neither the Company nor the sender accepts any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments.
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
The text was updated successfully, but these errors were encountered: