git.iko.soy/typeable/oauth2-proxy
on master help sign in
Merge pull request #133 from sricola/master
7ba51baJehiah Czebotar
README.md+4−5
@@ -42,13 +42,12 @@ For Google, the registration steps are:
421. Create a new project: https://console.developers.google.com/project
421. Create a new project: https://console.developers.google.com/project
432. Under "APIs & Auth", choose "Credentials"
432. Under "APIs & Auth", choose "Credentials"
443. Now, choose "Create new Client ID"
443. Now, choose "Create new Client ID"
45− * The Application Type should be **Web application**
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**
46− * Enter your domain in the Authorized Javascript Origins `https://internal.yourcompany.com`
47+ * On the next screen, leaving **Web Application** checked, enter your domain in the Authorized Javascript Origins `https://internal.yourcompany.com`
47 * Enter the correct Authorized Redirect URL `https://internal.yourcompany.com/oauth2/callback`
48 * Enter the correct Authorized Redirect URL `https://internal.yourcompany.com/oauth2/callback`
48 * NOTE: `oauth2_proxy` will _only_ callback on the path `/oauth2/callback`
49 * NOTE: `oauth2_proxy` will _only_ callback on the path `/oauth2/callback`
49−4. Under "APIs & Auth" choose "Consent Screen"
50− * Fill in the necessary fields and Save (this is _required_)
51−5. Take note of the **Client ID** and **Client Secret**
50+4. Take note of the **Client ID** and **Client Secret**
52
51
53It's recommended to refresh sessions on a short interval (1h) with `cookie-refresh` setting which validates that the account is still authorized.
52It's recommended to refresh sessions on a short interval (1h) with `cookie-refresh` setting which validates that the account is still authorized.
54
53