Update auto-generated properties

Repository: openmicroscopy/ome-documentation
Already up-to-date.

Generated by OMERO-5.1-merge-docs-autogen#71 (http://ci.openmicroscopy.org/job/OMERO-5.1-merge-docs-autogen/71/)

omero/sysadmins/config.txt

@@ -58,7 +58,8 @@ editor.
 
 .. note::
     Please use the **escape sequence** ``\"`` for nesting double quotes (e.g.
-    ``"[\"foo\", \"bar\"]"``) or wrap with ``'`` (e.g. ``'["foo", "bar"]'``).
+    ``"[\"foo\", \"bar\"]"``) or wrap with ``'`` (e.g. ``'["foo",
+    "bar"]'``).
 
 Examples of doing this are on the main :doc:`Unix <unix/server-installation>`
 and :doc:`Windows <windows/server-installation>` pages, as well as the
@@ -110,7 +111,7 @@ Default: `omero`
 omero.db.patch
 ^^^^^^^^^^^^^^
 
-Default: `9`
+Default: `10`
 
 .. property:: omero.db.poolsize
 
@@ -1175,6 +1176,13 @@ Default: `(int8and(permissions,%s) = %s)`
 
 omero.security.keyStore
 ^^^^^^^^^^^^^^^^^^^^^^^
+Whether to ignore the case of the user name during login (`true` or
+`false`). Default: `false` (JSmith and jsmith will be considered two
+different users).
+.. warning::
+   Before enabling this feature, lower the case of all user names in OMERO
+   (`omename` column in the `experimenter` table). It is the system
+   administrator's responsibility to handle any user name clashes.
 A keystore is a database of private keys and their associated X.509
 certificate chains authenticating the corresponding public keys.
 A keystore is mostly needed if you are doing client-side certificates
@@ -1407,7 +1415,7 @@ omero.web.logdir
 
 A path to the custom log directory.
 
-Default: ``/opt/hudson/workspace/OMERO-5.1-latest-docs-autogen/OMERO.server/var/log`` 
+Default: ``/opt/hudson/workspace/OMERO-5.1-merge-docs-autogen/OMERO.server/var/log`` 
 
 
 .. property:: omero.web.login_logo