Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/google-error.md

14 lines
625 B
Markdown
Raw Normal View History

config_error.html: Use render_markdown_path for error content.
2017-08-17 11:49:19 +02:00
You are using the **Google auth backend**, but it is not properly
configured. Please check the following:
auth: Migrate google auth to python-social-auth. This replaces the two custom Google authentication backends originally written in 2012 with using the shared python-social-auth codebase that we already use for the GitHub authentication backend. These are: * GoogleMobileOauth2Backend, the ancient code path for mobile authentication last used by the EOL original Zulip Android app. * The `finish_google_oauth2` code path in zerver/views/auth.py, which was the webapp (and modern mobile app) Google authentication code path. This change doesn't fix any known bugs; its main benefit is that we get to remove hundreds of lines of security-sensitive semi-duplicated code, replacing it with a widely trusted, high quality third-party library.
2019-02-02 16:51:26 +01:00
* You have created a Google Oauth2 client and enabled the Identity Toolkit API.
config_error.html: Use render_markdown_path for error content.
2017-08-17 11:49:19 +02:00
You can create OAuth2 apps at [the Google developer console](https://console.developers.google.com).
* You have configured your OAuth2 client to allow redirects to your
templates: Correct sample Google authorized redirect URI. The required URI was changed in #11450. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-12-22 00:49:30 +01:00
server's Google auth URL: `{{ root_domain_uri }}/complete/google/`.
config_error.html: Use render_markdown_path for error content.
2017-08-17 11:49:19 +02:00
auth: Allow setting GOOGLE_OAUTH2_CLIENT_ID from dev-secrets. This makes it much more convenient to use Google/GitHub authentication in a Zulip development environment for testing; one only has to set it up once.
2019-06-13 21:30:55 +02:00
* You have set `{{ client_id_key_name }}` in `{{ settings_path }}` and
auth: Migrate google auth to python-social-auth. This replaces the two custom Google authentication backends originally written in 2012 with using the shared python-social-auth codebase that we already use for the GitHub authentication backend. These are: * GoogleMobileOauth2Backend, the ancient code path for mobile authentication last used by the EOL original Zulip Android app. * The `finish_google_oauth2` code path in zerver/views/auth.py, which was the webapp (and modern mobile app) Google authentication code path. This change doesn't fix any known bugs; its main benefit is that we get to remove hundreds of lines of security-sensitive semi-duplicated code, replacing it with a widely trusted, high quality third-party library.
2019-02-02 16:51:26 +01:00
`social_auth_google_secret` in `{{ secrets_path }}`.
docs: Modify Google and GitHub instructions for auth setup. In auth setup, if you're at the error page you may be inclined to refresh the page once setting up auth after restarting the server, but the error page is a static page, so add instructions to go back to the login pages again and try the auth flow from there.
2017-08-28 19:31:48 +02:00
* Navigate back to the login page and attempt the Google auth flow again.