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
If the system clock drifts more than 30 seconds apart from the OPEN API Edgegrid server, the user will get an authentication error. This error not caught in almost any CLI package (most return very ugly errors) so instead of having to patch all CLI modules it would be great if the main CLI could verify this.
For example in MacOS or linux you could run this command to verify how far apart your local clock is:
AA=curl -q http://time.akamai.com/;BB=date +%s;echo "Your time drift is: $(($AA-$BB)) seconds"
The text was updated successfully, but these errors were encountered:
If the system clock drifts more than 30 seconds apart from the OPEN API Edgegrid server, the user will get an authentication error. This error not caught in almost any CLI package (most return very ugly errors) so instead of having to patch all CLI modules it would be great if the main CLI could verify this.
You can easily test if your clock is in sync by using Akamai's Time reference server time.akamai.com. See https://developer.akamai.com/legacy/learn/Akamai_Time_Reference/AkamaiTimeReference.html
For example in MacOS or linux you could run this command to verify how far apart your local clock is:
AA=
curl -q http://time.akamai.com/
;BB=date +%s
;echo "Your time drift is: $(($AA-$BB)) seconds"The text was updated successfully, but these errors were encountered: