For a language agnostic overview of authentication on Google Cloud, see Authentication Overview.
If you’re running in a Google Virtual Machine Environment (Compute Engine, App Engine, Cloud Run, Cloud Functions), authentication should “just work”.
If you’re developing locally, the easiest way to authenticate is using the Google Cloud SDK:
$ gcloud auth application-default login
Note that this command generates credentials for client libraries. To authenticate the CLI itself, use:
$ gcloud auth login
gcloud auth loginwas used for both use cases. If your
gcloudinstallation does not support the new command, please update it:
$ gcloud components update
If you’re running your application elsewhere, you should download a service account JSON keyfile and point to it using an environment variable:
$ export GOOGLE_APPLICATION_CREDENTIALS="/path/to/keyfile.json"
Every package uses a
as a base for interacting with an API.
from google.cloud import datastore client = datastore.Client()
Passing no arguments at all will “just work” if you’ve followed the instructions in the Overview. The credentials are inferred from your local environment by using Google Application Default Credentials.
Credential Discovery Precedence¶
The Application Default Credentials discussed above can be useful if your code needs to run in many different environments or if you just don’t want authentication to be a focus in your code.
However, you may want to be explicit because
your code will only run in one place
you may have code which needs to be run as a specific service account every time (rather than with the locally inferred credentials)
you may want to use two separate accounts to simultaneously access data from different projects
In these situations, you can create an explicit
Credentials object suited to your environment.
After creation, you can pass it directly to a
client = Client(credentials=credentials)
To create a credentials object, follow the google-auth-guide.
Google Compute Engine Environment¶
These credentials are used in Google Virtual Machine Environments. This includes most App Engine runtimes, Compute Engine, Cloud Functions, and Cloud Run.
from google.auth import compute_engine credentials = compute_engine.Credentials()
A service account is stored in a JSON keyfile.
from google.oauth2 import service_account credentials = service_account.Credentials.from_service_account_file( '/path/to/key.json')
A JSON string or dictionary:
import json from google.oauth2 import service_account json_account_info = json.loads(...) # convert JSON to dictionary credentials = service_account.Credentials.from_service_account_info( json_account_info)
Previously the Google Cloud Console would issue a PKCS12/P12 key for your service account. This library does not support that key format. You can generate a new JSON key for the same service account from the console.
User Accounts (3-legged OAuth 2.0) with a refresh token¶
The majority of cases are intended to authenticate machines or workers rather than actual user accounts. However, it’s also possible to call Google Cloud APIs with a user account via OAuth 2.0.
A production application should use a service account,
but you may wish to use your own personal user account when first
getting started with the
The simplest way to use credentials from a user account is via
Application Default Credentials using
gcloud auth application-default login
(as mentioned above) and
import google.auth credentials, project = google.auth.default()
This will still follow the precedence described above, so be sure none of the other possible environments conflict with your user provided credentials.
Setting up a Service Account¶
If your application is not running on a Google Virtual Machine Environment, you need a Service Account. See Creating a Service Account.
Using Google Compute Engine¶
If your code is running on Google Compute Engine, using the inferred Google Application Default Credentials will be sufficient for retrieving credentials.
However, by default your credentials may not grant you access to the services you intend to use. Be sure when you set up the GCE instance, you add the correct scopes for the APIs you want to access:
For scopes for specific APIs see OAuth 2.0 Scopes for Google APIs