https://connect.hyland.com/t5/nuxeo-forum/gcp-bucket-token-issue/m-p/321778#M8779 <P>We are having an issue with GCPbinaries package. After the server has been up for a while, we begin to get the following error in the logs: <STRONG>OAuth2Credentials instance does not support refreshing the access token. An instance with a new access token should be used, or a derived type that supports refreshing.</STRONG></P> <P>Once we restart the server, the error goes away, which we assume reauthenticates/refreshes the token. Is there a way to autorefresh the token, or are there specific settings in GCP we should use to allow the token to refresh? A server log and obfuscated GCP auth json attached for reference.</P> <P>Has anyone seen this before and our have tips on resolving?</P> Tue, 19 May 2020 10:01:27 GMT Robert_Smith 2020-05-19T10:01:27Z https://connect.hyland.com/t5/nuxeo-forum/gcp-bucket-token-issue/m-p/321778#M8779 <P>We are having an issue with GCPbinaries package. After the server has been up for a while, we begin to get the following error in the logs: <STRONG>OAuth2Credentials instance does not support refreshing the access token. An instance with a new access token should be used, or a derived type that supports refreshing.</STRONG></P> <P>Once we restart the server, the error goes away, which we assume reauthenticates/refreshes the token. Is there a way to autorefresh the token, or are there specific settings in GCP we should use to allow the token to refresh? A server log and obfuscated GCP auth json attached for reference.</P> <P>Has anyone seen this before and our have tips on resolving?</P> Tue, 19 May 2020 10:01:27 GMT https://connect.hyland.com/t5/nuxeo-forum/gcp-bucket-token-issue/m-p/321778#M8779 Robert_Smith 2020-05-19T10:01:27Z