You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by mm...@apache.org on 2019/04/01 16:38:28 UTC
[pulsar] branch master updated: Added information about generate
key location for jwt. (#3927)
This is an automated email from the ASF dual-hosted git repository.
mmerli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 08a4e80 Added information about generate key location for jwt. (#3927)
08a4e80 is described below
commit 08a4e80be797a57e24128f8cd1f1358224ba487e
Author: Yuvaraj L <uv...@gmail.com>
AuthorDate: Mon Apr 1 22:08:24 2019 +0530
Added information about generate key location for jwt. (#3927)
* Added information about generate key location for jwt. Added information about generating base64 encoded key.
* Fixed for 2.2.1 version
---
site2/docs/security-token-admin.md | 6 ++++++
site2/website/versioned_docs/version-2.2.1/security-token-admin.md | 7 ++++++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/site2/docs/security-token-admin.md b/site2/docs/security-token-admin.md
index 07e5d43..54043da 100644
--- a/site2/docs/security-token-admin.md
+++ b/site2/docs/security-token-admin.md
@@ -47,9 +47,14 @@ the brokers to allow them to validate the clients.
#### Creating a secret key
+> Output file will be generated in the root of your pulsar installation directory. You can also provide absolute path for the output file.
```shell
$ bin/pulsar tokens create-secret-key --output my-secret.key
```
+To generate base64 encoded private key
+```shell
+$ bin/pulsar tokens create-secret-key --output /opt/my-secret.key --base64
+```
### Public/Private keys
@@ -57,6 +62,7 @@ With public/private, we need to create a pair of keys.
#### Creating a key pair
+> Output file will be generated in the root of your pulsar installation directory. You can also provide absolute path for the output file.
```shell
$ bin/pulsar tokens create-key-pair --output-private-key my-private.key --output-public-key my-public.key
```
diff --git a/site2/website/versioned_docs/version-2.2.1/security-token-admin.md b/site2/website/versioned_docs/version-2.2.1/security-token-admin.md
index 4caea62..2d52a85 100644
--- a/site2/website/versioned_docs/version-2.2.1/security-token-admin.md
+++ b/site2/website/versioned_docs/version-2.2.1/security-token-admin.md
@@ -47,17 +47,22 @@ use it to generate the client tokens. This key will be also configured to
the brokers to allow them to validate the clients.
#### Creating a secret key
-
+> Output file will be generated in the root of your pulsar installation directory. You can also provide absolute path for the output file.
```shell
$ bin/pulsar tokens create-secret-key --output my-secret.key
```
+To generate base64 encoded private key
+```shell
+$ bin/pulsar tokens create-secret-key --output /opt/my-secret.key --base64
+```
### Public/Private keys
With public/private, we need to create a pair of keys.
#### Creating a key pair
+> Output file will be generated in the root of your pulsar installation directory. You can also provide absolute path for the output file.
```shell
$ bin/pulsar tokens create-key-pair --output-private-key my-private.key --output-public-key my-public.key
```