Issue with APM and Google Auth time sync

We recently configured our APM to use AD credentials plus a Google authentication token. I have found out that if we attempt to log in immediately after generating the token we get a “session cannot be established” error. However if we wait until the token has 50% of its TTL or less remaining authentication works fine.

Is there away to adjust the time sync fuzz on the F5?

What device are you using to generate the token. Make sure your f5 is time sync’d with a global source. If you are generating tokens on a smart device make sure their times aren’t off. The Google client for android has a time phase capability because not all carriers have a common time. Contacting the carriers does no good. Good luck.