Skip to content

Commit

Permalink
Merge pull request #48 from rabernat/patch-1
Browse files Browse the repository at this point in the history
clarify authentication
  • Loading branch information
martindurant authored Dec 8, 2017
2 parents 24e122e + 349d065 commit 428f2f4
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ This software is alpha, use at your own risk.

Please file issues and requests on github_ and we welcome pull requests.

.. _github: https://github.com/martindurant/gcsfs/issues
.. _github: https://github.com/dask/gcsfs/issues

Installation
------------
Expand Down Expand Up @@ -79,8 +79,8 @@ Two modes of authentication are supported:

- if ``token=None``, GCSFS will attempt to use your default gcloud
credentials or, if that fails,
you will be given a "device code", which you must
enter into a browser where you are logged in with your Google identity.
will print a "device code" and a link you must follow to
authenticate with your Google identity.

- if ``token='cloud'``, we assume we are running within google (compute
or container engine) and fetch the credentials automatically from the
Expand All @@ -90,7 +90,8 @@ Two modes of authentication are supported:
gcloud_ utility; this is either a python dictionary, or the name of a file
containing the JSON returned by logging in with the gcloud CLI tool. On
a posix system this may be at
``~/.config/gcloud/application_default_credentials.json``
``~/.config/gcloud/application_default_credentials.json`` or
``~/.config/gcloud/legacy_credentials/<YOUR GOOGLE USERNAME>/adc.json``

Authorizations are cached in a local file, for a given project/access level, so
you should not need to authorize again.
Expand Down

0 comments on commit 428f2f4

Please sign in to comment.