Basically I configured the oauth flux in Gemini Enterprise. It can generate a Access token if the previous one expired when creating a new chat. The problem is in older chats, given that each chat has its Access token expired and associated to the session state, the Gemini Enterprise doesn’t update their Access token, even if i refresh the page or something like that, on the session state making the tool inside the agent that need the Access token broke.
Is this behavior normal? Or maybe is something that i miss understood/ configurated when generating the oauth?
We’re seeing this on Gemini Enterprise with an ADK agent (google-adk 2.12, ADK registration, not A2A) that reads a user OAuth token from session state (temp:<authorization id>) on every request. New chats work; we’d like to confirm whether long-lived chats keep a stale token. This issue was closed as completed, but the last comment says no refresh logic exists, and the linked fix (#5578) was closed unmerged. Could it be reopened, and could someone confirm whether the token renewal for existing chats is expected from Gemini Enterprise (server side) or from ADK? A pointer to the intended pattern for agents (re-read temp: each turn, or the credential layer mentioned in #5578’s review) would help.