Deployed 69d1f6d7b to main with MkDocs 1.6.1 and mike 2.2.0

main/api/spec/index.html

@@ -15159,7 +15159,9 @@ string
 </p>
 <p>
 <p>SecretServerProvider provides access to authenticate to a secrets provider server.
-See: <a href="https://github.com/DelineaXPM/tss-sdk-go/blob/main/server/server.go">https://github.com/DelineaXPM/tss-sdk-go/blob/main/server/server.go</a>.</p>
+See: <a href="https://github.com/DelineaXPM/tss-sdk-go/blob/main/server/server.go">https://github.com/DelineaXPM/tss-sdk-go/blob/main/server/server.go</a>.
+Authentication requires either Token, or both Username and Password. If Token is
+set it takes precedence and Username/Password are ignored.</p>
 </p>
 <table>
 <thead>
@@ -15179,7 +15181,9 @@ SecretServerProviderRef
 </em>
 </td>
 <td>
-<p>Username is the secret server account username.</p>
+<em>(Optional)</em>
+<p>Username is the secret server account username.
+Required unless Token is set.</p>
 </td>
 </tr>
 <tr>
@@ -15192,7 +15196,25 @@ SecretServerProviderRef
 </em>
 </td>
 <td>
-<p>Password is the secret server account password.</p>
+<em>(Optional)</em>
+<p>Password is the secret server account password.
+Required unless Token is set.</p>
+</td>
+</tr>
+<tr>
+<td>
+<code>token</code></br>
+<em>
+<a href="#external-secrets.io/v1.SecretServerProviderRef">
+SecretServerProviderRef
+</a>
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>Token is an access token used to authenticate to the secret server,
+as an alternative to Username and Password. When set, Username and
+Password are not required and are ignored.</p>
 </td>
 </tr>
 <tr>
@@ -15257,7 +15279,7 @@ CAProvider
 </p>
 <p>
 <p>SecretServerProviderRef references a value that can be specified directly or via a secret
-for a SecretServerProvider.</p>
+for a SecretServerProvider. Exactly one of Value or SecretRef must be set.</p>
 </p>
 <table>
 <thead>

main/provider/secretserver/index.html

@@ -3911,6 +3911,17 @@
     </span>
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#authenticating-with-an-access-token" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Authenticating with an Access Token
+      
+    </span>
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -5236,6 +5247,17 @@
     </span>
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#authenticating-with-an-access-token" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Authenticating with an Access Token
+      
+    </span>
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -5492,6 +5514,26 @@ spec.provider.secretserver.password.value: "yourpassword" <br /></p>
 <span class="w">          </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">&lt;NAME_OF_K8S_SECRET&gt;</span>
 <span class="w">          </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">&lt;KEY_IN_K8S_SECRET&gt;</span>
 </code></pre></div></p>
+<h2 id="authenticating-with-an-access-token">Authenticating with an Access Token</h2>
+<p>As an alternative to <code>username</code> and <code>password</code>, you can authenticate using a pre-issued
+access token via the <code>token</code> field. This is useful when username/password login is not
+available (for example, on-prem installations with domain accounts). When <code>token</code> is set,
+<code>username</code> and <code>password</code> are not required and are ignored.</p>
+<p>Like the other credentials, the token can be provided directly via the <code>value</code> field or by
+referencing a Kubernetes secret via <code>secretRef</code>.</p>
+<div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">external-secrets.io/v1</span>
+<span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">SecretStore</span>
+<span class="nt">metadata</span><span class="p">:</span>
+<span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">secret-server-store</span>
+<span class="nt">spec</span><span class="p">:</span>
+<span class="w">  </span><span class="nt">provider</span><span class="p">:</span>
+<span class="w">    </span><span class="nt">secretserver</span><span class="p">:</span>
+<span class="w">      </span><span class="nt">serverURL</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;https://yourtenantname.secretservercloud.com&quot;</span><span class="w">  </span><span class="c1"># or &quot;https://yourtenantname.delinea.app&quot; for Platform</span>
+<span class="w">      </span><span class="nt">token</span><span class="p">:</span>
+<span class="w">        </span><span class="nt">secretRef</span><span class="p">:</span>
+<span class="w">          </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">&lt;NAME_OF_K8S_SECRET&gt;</span>
+<span class="w">          </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">&lt;KEY_IN_K8S_SECRET&gt;</span>
+</code></pre></div>
 <h2 id="referencing-secrets">Referencing Secrets</h2>
 <p>Secrets can be referenced using four different key formats in the <code>remoteRef.key</code> field:</p>
 <table>