However, this is a good suggestion and we'll investigate if this functionality can be added in a future version of the TMS Cloud Pack.
I will not friend, try to explain better, I'm using Google translate, When we open a browser the email I used to log into Google Drive is connected, if the user logs off my system stops working and asks the login screen again and authorization when I try to send a file to the cloud. I would use my system with my account on my clients, without them having access to it, I believe it is problem session in browsers. Any suggestions on how to solve?
Please note that authentication tokens are not stored in browser sessions.
Have you tried using the SaveTokens and LoadTokens calls to save/load authentication tokens locally?
I'm using, I copied the DEMO and work on it from time to time he calls once the password for authentication, do not know what can be ocorrento for him "lose" authentication and need to authenticate again. Very strange.
The authentication tokens can expire from time to time.
If the refresh does not work for some reason there is no other option than to request new tokens through authentication.
Expiration and validity of tokens is controlled by the Google API, we have no access to this.
We have an account of 1TB to send the backup of our customers, each to a folder. I believe that would not give to share and we would compel our client to have a gmail account to work. But I appreciate the explanations.
I think this is really a limitation of the Google API.
Only with a service with a non-expiring token you could implement this by hardcoding your access-token in the app (although you'll need to check with the service specifications whether this approach is in line with their licensing terms)