Google Cloud Platform (GCP) recently updated its credential policy and eliminated non-expiring user personal credentials. Credentials will now expire after 16 hours. This change improves platform security, and many users haven’t noticed a difference in their GCP experience.
However, account holders running long-duration jobs, scripts, or workloads have had to either redesign their processes to accommodate reauthentication every 16 hours or move away from long-term personal credentials. Others are still adapting to this new requirement.
To address this disruption to workflows, University IT (UIT) Hosting Services is providing a temporary exception to the 16-hour credential expiration policy through March 2027. This exception window allows users additional time to transition away from long-term personal credentials.
Temporary non-expiring credentials
Account holders whose automated tooling can’t be re-architected right away can opt in to a non-expiring credential exception.
The exception lasts until March 2027 and can be requested by submitting an Exception Request. It is intended as a temporary bridge, not a permanent option. The additional time allows account holders to move away from long-term personal credentials, for example, by switching to a service account. The Hosting Services team can help you identify the recommended approach for your use case.
Request an exception
To receive temporary non-expiring credential access:
- Submit an Exception Request to Hosting Services.
- Describe your GCP use case and why you need the exception.
- Confirm that you are not working with High Risk Data.
- Accept the risk of using long-term credentials in the interim.
After March 2027
Exception users will return to the 16-hour expiration policy. Hosting Services will reassess whether the exception is still necessary for affected account holders.
Questions? Submit a Help request to the Hosting Services team.

