Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
From my understanding, when using the Drive Java API it is recommended to build an instance of the Drive class and then store it so that it can then be shared by other threads. If the process that holds this reference to the Drive instance is a long running processes (i.e. indefinite) will the session (?) eventually expire and require authentication again, or are the credentials passed with every request?
The Drive API uses OAuth 2.0 as the authorization mechanism and that involves passing an access token with every request.
Access tokens are short-lived and expire after about 1 hour. When that happens, your application has to request a new access token by using the refresh token that is retrieved the first time the user authorizes the app.
All of this is performed automatically by the Java client library for Google Drive and is documented at https://developers.google.com/drive/about-auth
The documentation also includes a complete Java sample application for Google Drive that you can use as reference:
https://developers.google.com/drive/examples/java