diff options
| author | Patrick Cloke <clokep@users.noreply.github.com> | 2020-12-18 13:09:45 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-12-18 13:09:45 -0500 |
| commit | 4218473f9ea6a2680c21e96368dfe9c06271c8a4 (patch) | |
| tree | 3203110c1f345bff5592dbc90fb6749dea1597ee /docs/dev/cas.md | |
| parent | Send the location of the web client to the IS when inviting via 3PIDs. (#8930) (diff) | |
| download | synapse-4218473f9ea6a2680c21e96368dfe9c06271c8a4.tar.xz | |
Refactor the CAS handler in prep for using the abstracted SSO code. (#8958)
This makes the CAS handler look more like the SAML/OIDC handlers: * Render errors to users instead of throwing JSON errors. * Internal reorganization.
Diffstat (limited to 'docs/dev/cas.md')
| -rw-r--r-- | docs/dev/cas.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/dev/cas.md b/docs/dev/cas.md index f8d02cc82c..592b2d8d4f 100644 --- a/docs/dev/cas.md +++ b/docs/dev/cas.md @@ -31,7 +31,7 @@ easy to run CAS implementation built on top of Django. You should now have a Django project configured to serve CAS authentication with a single user created. -## Configure Synapse (and Riot) to use CAS +## Configure Synapse (and Element) to use CAS 1. Modify your `homeserver.yaml` to enable CAS and point it to your locally running Django test server: @@ -51,9 +51,9 @@ and that the CAS server is on port 8000, both on localhost. ## Testing the configuration -Then in Riot: +Then in Element: -1. Visit the login page with a Riot pointing at your homeserver. +1. Visit the login page with a Element pointing at your homeserver. 2. Click the Single Sign-On button. 3. Login using the credentials created with `createsuperuser`. 4. You should be logged in. |