# tmsh show sys ver
Sys::Version
Main Package
Product BIG-IP
Version 14.1.0.3
Build 0.0.6
Edition Point Release 3
Date Mon Mar 25 17:15:27 PDT 2019
SUMMARY
Some of my logs fail to be sent to Security Hub. Checking the restnoded logs, I see that the token is expired.
Ideally, refreshtoken interval needs to be shorter than the expiry time. What is the expected token validity duration? Logs are below.
EXPECTED RESULTS
no error when sending logs to security hub
ACTUAL RESULTS
Error "The security token included in the request is expired" when trying to send logs to Security hub. Looks like startTokenRefresh is set to 8 hours.
The session duration is set to default 1 hr. However, when I grab the creds, expiration is about 6 hrs after lastupdated....not sure why but 8 hrs interval for refreshtoken will likely result in some expired token errors. Some options are to extend the session duration to be 12hrs or try making the refreshtoken interval shorter.
ISSUE TYPE
VERSION
BIGIP VERSION
SUMMARY
Some of my logs fail to be sent to Security Hub. Checking the restnoded logs, I see that the token is expired.
Ideally, refreshtoken interval needs to be shorter than the expiry time. What is the expected token validity duration? Logs are below.
EXPECTED RESULTS
no error when sending logs to security hub
ACTUAL RESULTS
Error "The security token included in the request is expired" when trying to send logs to Security hub. Looks like startTokenRefresh is set to 8 hours.
cat /var/log/restnoded/restnoded.log | grep -i token
aws iam get-role --role-name BIGIPSecurityHubRole
The session duration is set to default 1 hr. However, when I grab the creds, expiration is about 6 hrs after lastupdated....not sure why but 8 hrs interval for refreshtoken will likely result in some expired token errors. Some options are to extend the session duration to be 12hrs or try making the refreshtoken interval shorter.
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/BIGIPSecurityHubRole