Update from https://github.comt/treeverse/lakeFS/commit/3b57c4a0444e4…

…4a896aa99c90e727e7396a3ae70

v1.48/assets/js/search-data.json

@@ -29,7 +29,7 @@
   },"4": {
     "doc": "Access Control Lists (ACLs) -Deprecated-",
     "title": "Basic Auth Functionality",
-    "content": "New lakeFS versions will provide basic auth functionality featuring a single Admin user with a single set of credentials. Existing lakeFS installations that have a single user and a single set of credentials will migrate seamlessly to the new version. Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate (more details here) . ",
+    "content": "New lakeFS versions will provide basic auth functionality featuring a single Admin user with a single set of credentials. Existing lakeFS installations that have a single user and a single set of credentials will migrate seamlessly to the new version. Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate (more details here) . Credentials Replacement . In a single user setup, replacing credentials can be done as follows: . | Delete the existing user: lakectl auth users delete --id <user-id> . | Shut down the lakeFS server - Required for invalidating the old credentials on the server | Create a new user, with the same name and new credentials: lakefs superuser --user-name <user-id> . This will generate a new set of credentials, and will print it out to the screen: . credentials: access_key_id: *** (omitted) secret_access_key: *** (omitted) . | Re-run lakeFS server | . Calling the superuser command with pre-defined --access-key-id and --secret-access-key is possible, but should be done with caution. Make sure that --secret-access-key is not empty, as providing an access key without a secret key will trigger an ACL import flow (see Migration of existing user). In case you already deleted the user by following step (1), this import operation will fail and result in an unrecoverable state, from which a clean installation is the only way out. ",
     "url": "/v1.48/security/access-control-lists.html#basic-auth-functionality",
 
     "relUrl": "/security/access-control-lists.html#basic-auth-functionality"

v1.48/security/access-control-lists.html

@@ -598,6 +598,42 @@ <h2 id="basic-auth-functionality">
 Existing lakeFS installations that have a single user and a single set of credentials will migrate seamlessly to the new version.<br />
 Installations that have more than one user / credentials will require to run a command and choose which set of user + credentials to migrate 
 (more details <a href="#migration-of-existing-user">here</a>)</p>
+<h3 id="credentials-replacement">
+
+
+    <a href="#credentials-replacement" class="anchor-heading"><svg viewBox="0 0 16 16" aria-hidden="true"><use xlink:href="#svg-link"></use></svg></a> Credentials Replacement
+
+
+</h3>
+
+
+<p>In a single user setup, replacing credentials can be done as follows:</p>
+<ol>
+  <li>Delete the existing user:
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> lakectl auth <span class="nb">users </span>delete <span class="nt">--id</span> &lt;user-id&gt;
+</code></pre></div>    </div>
+  </li>
+  <li>Shut down the lakeFS server - Required for invalidating the old credentials on the server</li>
+  <li>Create a new user, with the same name and new credentials:
+    <div class="language-shell highlighter-rouge"><div class="highlight"><pre class="highlight"><code> lakefs superuser <span class="nt">--user-name</span> &lt;user-id&gt;
+</code></pre></div>    </div>
+    <p>This will generate a new set of credentials, and will print it out to the screen:</p>
+    <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code> credentials:
+   access_key_id: *** (omitted)
+   secret_access_key: *** (omitted)
+</code></pre></div>    </div>
+  </li>
+  <li>Re-run lakeFS server</li>
+</ol>
+
+<blockquote class="note warning">
+  <p>Calling the <code class="language-plaintext highlighter-rouge">superuser</code> command with pre-defined <code class="language-plaintext highlighter-rouge">--access-key-id</code> and <code class="language-plaintext highlighter-rouge">--secret-access-key</code> is possible,
+but should be done with caution. Make sure that <code class="language-plaintext highlighter-rouge">--secret-access-key</code> is <strong>not empty</strong>,
+as providing an access key without a secret key will trigger an ACL import flow
+(see <a href="#migration-of-existing-user">Migration of existing user</a>).
+In case you already deleted the user by following step (1), this import operation will <strong>fail</strong> and result in an 
+<strong>unrecoverable</strong> state, from which a clean installation is the only way out.</p>
+</blockquote>
 <h2 id="acls">