From 8c530f30e32828546d89e3241b3d2bdc86099606 Mon Sep 17 00:00:00 2001 From: Mateusz Mandera Date: Wed, 5 Jul 2023 11:08:11 +0200 Subject: [PATCH] docs: Update SCIM doc to not mention add_scim_client. add_scim_client was removed in 55342efd33cc482daecdf9d0f560b4f32122540f. --- docs/production/scim.md | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/docs/production/scim.md b/docs/production/scim.md index 252ab8a806..29ccd9ffb6 100644 --- a/docs/production/scim.md +++ b/docs/production/scim.md @@ -18,23 +18,6 @@ The Zulip server-side configuration is straightforward: 1. Pick a client name for your SCIM client. This name is internal to your Zulip configuration, so the name of your IdP provider is a good choice. We'll use `okta` in the examples below. -1. First a SCIM client entry needs to be added to the database. Run - `manage.py add_scim_client -r `. For - example, if your organization is hosted on a subdomain - (`subdomain.zulip.example.com`): - - ```bash - /home/zulip/deployments/current/manage.py add_scim_client okta -r 'subdomain' - ``` - - Or your organization is hosted on the root domain (`zulip.example.com`): - - ```bash - /home/zulip/deployments/current/manage.py add_scim_client okta -r "" - ``` - - See the [management command documentation](./management-commands.md) - for details on how to run management commands. 1. Configure the Zulip server by adding a `SCIM_CONFIG` block to your `/etc/zulip/settings.py`: