Skip to content

Commit

Permalink
docs: documented auth-token supported signing methods
Browse files Browse the repository at this point in the history
    Resolves issue etcd-io#706 by moving the documented signing methods from v3.4/op-guide/configuration.md to
    v3.6/op-guide/configuration.md

Signed-off-by: edragone <edragone07@gmail.com>
  • Loading branch information
edragone committed Nov 7, 2023
1 parent c34ecb0 commit 941cfe1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/en/docs/v3.6/op-guide/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ The list of flags provided below may not be up-to-date due to ongoing developmen

```nocode
--auth-token 'simple'
Specify a v3 authentication token type and its options ('simple' or 'jwt').
Specify a v3 authentication token type and token specific options, especially for JWT. Its format is "type,var1=val1,var2=val2,...". Possible type is 'simple' or 'jwt'. Possible variables are 'sign-method' for specifying a sign method of jwt (its possible values are 'ES256', 'ES384', 'ES512', 'HS256', 'HS384', 'HS512', 'RS256', 'RS384', 'RS512', 'PS256', 'PS384', or 'PS512'), 'pub-key' for specifying a path to a public key for verifying jwt, 'priv-key' for specifying a path to a private key for signing jwt, and 'ttl' for specifying TTL of jwt tokens.
--bcrypt-cost 10
Specify the cost / strength of the bcrypt algorithm for hashing auth passwords. Valid values are between 4 and 31.
--auth-token-ttl 300
Expand Down

0 comments on commit 941cfe1

Please sign in to comment.