Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clarify authentication #48

Merged
merged 3 commits into from
Dec 8, 2017
Merged

clarify authentication #48

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
95a30db
clarify authentication
rabernat Dec 8, 2017
f4fb5f3
Update index.rst
rabernat Dec 8, 2017
349d065
fix github link
rabernat Dec 8, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/source/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
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 goodle Google identity.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

goodle?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

goodle


- 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