From 3e2a2bf603f2c69b8a244cb77803abd2b661141f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=B4me=20Chilliet?= Date: Mon, 9 May 2022 10:15:33 +0200 Subject: [PATCH] Fix LDAP first configId information MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It starts at s01, no more empty configId for the first one. Signed-off-by: Côme Chilliet --- admin_manual/configuration_server/occ_command.rst | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/admin_manual/configuration_server/occ_command.rst b/admin_manual/configuration_server/occ_command.rst index 85477d19b..d27c02179 100644 --- a/admin_manual/configuration_server/occ_command.rst +++ b/admin_manual/configuration_server/occ_command.rst @@ -905,13 +905,7 @@ use the ``--force`` option to force it to check all active LDAP connections:: sudo -u www-data php occ ldap:check-user --force robert ``ldap:create-empty-config`` creates an empty LDAP configuration. The first -one you create has no ``configID``, like this example:: - - sudo -u www-data php occ ldap:create-empty-config - Created new configuration with configID '' - -This is a holdover from the early days, when there was no option to create -additional configurations. The second, and all subsequent, configurations +one you create has ``configID`` ``s01``, and all subsequent configurations that you create are automatically assigned IDs:: sudo -u www-data php occ ldap:create-empty-config