Skip to content

Commit beebf4d

Browse files
committed
Merge pull request #182 from funkymrrogers/master
Google UI changes
2 parents e4626c1 + 0fad1da commit beebf4d

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

README.md

+12-7
Original file line numberDiff line numberDiff line change
@@ -40,13 +40,18 @@ The provider can be selected using the `provider` configuration value.
4040
For Google, the registration steps are:
4141

4242
1. Create a new project: https://console.developers.google.com/project
43-
2. Under "APIs & Auth", choose "Credentials"
44-
3. Now, choose "Create new Client ID"
45-
* The Application Type should be **Web application** and click **Configure Consent Screen**
46-
* Fill out the appropriate details on the Consent Screen page and hit **Save**
47-
* On the next screen, leaving **Web Application** checked, enter your domain in the Authorized Javascript Origins `https://internal.yourcompany.com`
48-
* Enter the correct Authorized Redirect URL `https://internal.yourcompany.com/oauth2/callback`
49-
* NOTE: `oauth2_proxy` will _only_ callback on the path `/oauth2/callback`
43+
2. Choose the new project from the top right project dropdown (only if another project is selected)
44+
3. In the project Dashboard center pane, choose **"Enable and manage APIs"**
45+
4. In the left Nav pane, choose **"Credentials"**
46+
5. In the center pane, choose **"OAuth consent screen"** tab. Fill in **"Product name shown to users"** and hit save.
47+
6. In the center pane, choose **"Credentials"** tab.
48+
* Open the **"New credentials"** drop down
49+
* Choose **"OAuth client ID"**
50+
* Choose **"Web application"**
51+
* Application name is freeform, choose something appropriate
52+
* Authorized JavaScript origins is your domain ex: `https://internal.yourcompany.com`
53+
* Authorized redirect URIs is the location of oath2/callback ex: `https://internal.yourcompany.com/oauth2/callback`
54+
* Choose **"Create"**
5055
4. Take note of the **Client ID** and **Client Secret**
5156

5257
It's recommended to refresh sessions on a short interval (1h) with `cookie-refresh` setting which validates that the account is still authorized.

0 commit comments

Comments
 (0)