Skip to content

Commit

Permalink
docs: Delete redundant oauth-web.md (#1142)
Browse files Browse the repository at this point in the history
  • Loading branch information
parthea committed Dec 16, 2020
1 parent 4249a7b commit 70bc6c9
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 56 deletions.
2 changes: 1 addition & 1 deletion docs/README.md
Expand Up @@ -20,7 +20,7 @@ Learn how to use the Google API Python Client with these guides:
- [Auth](auth.md)
- [API Keys](api-keys.md)
- [OAuth 2.0](oauth.md)
- [OAuth 2.0 for Web Server Applications](oauth-web.md)
- [OAuth 2.0 for Web Server Applications](https://developers.google.com/identity/protocols/oauth2/web-server)
- [OAuth 2.0 for Installed Applications](oauth-installed.md)
- [OAuth 2.0 for Server to Server Applications](oauth-server.md)
- [Client Secrets](client-secrets.md)
Expand Down
2 changes: 1 addition & 1 deletion docs/api-keys.md
Expand Up @@ -2,7 +2,7 @@

When calling APIs that do not access private user data, you can use simple API keys. These keys are used to authenticate your application for accounting purposes. The Google Developers Console documentation also describes [API keys](https://developers.google.com/console/help/using-keys).

> Note: If you do need to access private user data, you must use OAuth 2.0. See [Using OAuth 2.0 for Installed Applications](oauth-installed.md), [Using OAuth 2.0 for Server to Server Applications](oauth-server.md), and [Using OAuth 2.0 for Web Server Applications](oauth-web.md) for more information.
> Note: If you do need to access private user data, you must use OAuth 2.0. See [Using OAuth 2.0 for Installed Applications](oauth-installed.md), [Using OAuth 2.0 for Server to Server Applications](oauth-server.md), and [Using OAuth 2.0 for Web Server Applications](https://developers.google.com/identity/protocols/oauth2/web-server) for more information.
## Using API Keys

Expand Down
54 changes: 0 additions & 54 deletions docs/oauth-web.md

This file was deleted.

0 comments on commit 70bc6c9

Please sign in to comment.