2024-02-15: the token in gitgnored oauth2.keys.json was deleted. Itwas in the GPhotosSync Project (daniel.lauzon@gmail.com) Google API Console/API & Services/Credentials.
The purpose of this package is to encapsulate authentication to Google APIs with OAuth2.
In particular we want to provision/verify refresh tokens locally for a developer, to test interacting with such a service.
This is meant to get local credententials, for local development (i.e. the OAuth callback is on http://127.0.0.1).
This library depends on the Google maintained google-auth-library package
The basics of Google's OAuth2 implementation is explained on Google Authorization and Authentication documentation.
npm publish --access public- Rename public methods
- Test
- Publish, use in gphotos-googleapis
- Specific validators or url
- Implement refreshTokensDB.json (-db)
- persist refresh token by account/id
- renovate
To identify a requested token with an sub/id field, we need to add https://www.googleapis.com/auth/userinfo.profile to our requested scopes. This is equivalent to the profile scope, and also provides us with a name,given_name,family_name,picture fields. You can also use openid as a requested scope, which will give ths sub,picture identification fields, but no name.
- setup
- generate
- validate
Some parts are harder to automate, so this description is still necessary
Before your application can use Google's OAuth 2.0 authentication system for user login, you must set up a project in the Google API Console to obtain OAuth 2.0 credentials and set an authentication callback (redirectUri).
- Goto Google API Console
- Create (or select an existing) Project
- Enable the API's you want to use in the APIs & Services Section/Library
- Go to APIs and Services / Credentials tab.
- Create credentials > OAuth client ID
- Set the authorized JavaScript origin to http://127.0.0.1 and the authorized redirect URL to http://127.0.0.1:8080/auth/google/callback. (The callback path can be any path you choose you choose)
- You can then copy the three pieces of information we need (or download the json credentials from the console)
- Client ID
- Client Secret
- Redirect URI's