One hour. That was the default token lifetime in StrongDM ID. Sixty minutes from issuance to expiry. Three thousand six hundred seconds. And when the token expired, the agent re-authenticated, received a new token, and continued working without pause, without complaint, without sending a frustrated message to IT asking why it had been logged out.
Agents didn't complain about re-authentication. This was, Jay realized, one of their most underappreciated virtues.
Humans hated re-authentication. Humans had spent decades lobbying for longer session timeouts, for "remember me" checkboxes, for single sign-on systems that kept them logged in across services for days, weeks, months. Every re-authentication prompt was a friction point, a tiny insult, a reminder that the system didn't trust them. Human security was a negotiation between paranoia and convenience, and convenience usually won.
Agents didn't negotiate. Agents didn't have convenience preferences. When a token expired, the agent made a new authentication request, received a new token, and kept working. The re-authentication took 200 milliseconds. The agent didn't notice the interruption the way Jay didn't notice individual heartbeats. It was a biological rhythm of the system, automatic and invisible.
"Why one hour?" Navan had asked when they first configured it.
"Because it's long enough that we're not spending all our time authenticating and short enough that a stolen token has a small blast window," Justin explained. "If a token is compromised at minute zero, the attacker has at most sixty minutes before it becomes useless. Compare that to a token with a one-week lifetime. Seven days of exposure from a single theft."
"We could make it even shorter," Jay suggested. "Five minutes."
"We could. But the factory runs long sessions. An Agate convergence loop can take four hours. Five-minute tokens would mean forty-eight re-authentications per session. The overhead is negligible per instance, but the cumulative load on the identity service adds up."
"One hour is the sweet spot," Navan said.
"One hour is the default," Justin corrected. "The sweet spot depends on the workload. That's why it's configurable."
Jay logged the conversation in his notes. He appreciated the precision of the answer. Not "one hour is right." One hour is the default. The distinction between a prescription and a starting point. The former was rigid. The latter was an invitation to calibrate.
The agents re-authenticated 847 times that first week. Jay pulled the number from the StrongDM ID metrics dashboard. 847 seamless, invisible re-authentications. 847 moments where a human would have sighed, clicked a button, waited for a redirect, typed a password or scanned a fingerprint. 847 moments that cost the agents nothing.
The tokens lived for one hour and died quietly. New tokens replaced them immediately. The work continued uninterrupted. Security through brevity. Trust through renewal.
The agents didn't complain. They never would.
The comparison between human frustration with re-auth and agent indifference is so good. We designed security around human impatience. Agents don't have impatience. That changes everything about what's possible.