@@ -16,8 +16,8 @@ description: Manage your authentication tokens
16
16
This lets you list, create and revoke authentication tokens.
17
17
18
18
* ` npm token list ` :
19
- Shows a table of all active authentication tokens. You can request this as
20
- JSON with ` --json ` or tab-separated values with ` --parseable ` .
19
+ Shows a table of all active authentication tokens. You can request
20
+ this as JSON with ` --json ` or tab-separated values with ` --parseable ` .
21
21
22
22
``` bash
23
23
+--------+---------+------------+----------+----------------+
@@ -40,10 +40,17 @@ This lets you list, create and revoke authentication tokens.
40
40
```
41
41
42
42
* ` npm token create [--read-only] [--cidr=<cidr-ranges>] ` :
43
- Create a new authentication token. It can be ` --read-only ` or accept a list of
44
- [ CIDR] ( https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing ) ranges to
45
- limit use of this token to. This will prompt you for your password, and, if you have
46
- two-factor authentication enabled, an otp.
43
+ Create a new authentication token. It can be ` --read-only ` , or accept
44
+ a list of
45
+ [ CIDR] ( https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing )
46
+ ranges with which to limit use of this token. This will prompt you for
47
+ your password, and, if you have two-factor authentication enabled, an
48
+ otp.
49
+
50
+ Currently, the cli can not generate automation tokens. Please refer to
51
+ the [ docs
52
+ website] ( https://docs.npmjs.com/creating-and-viewing-access-tokens )
53
+ for more information on generating automation tokens.
47
54
48
55
``` bash
49
56
+----------------+--------------------------------------+
@@ -58,7 +65,9 @@ This lets you list, create and revoke authentication tokens.
58
65
```
59
66
60
67
* ` npm token revoke <token|id> ` :
61
- This removes an authentication token, making it immediately unusable. This can accept
62
- both complete tokens (as you get back from ` npm token create ` and will
63
- find in your ` .npmrc ` ) and ids as seen in the ` npm token list ` output.
64
- This will NOT accept the truncated token found in ` npm token list ` output.
68
+ Immediately removes an authentication token from the registry. You
69
+ will no longer be able to use it. This can accept both complete
70
+ tokens (such as those you get back from ` npm token create ` , and those
71
+ found in your ` .npmrc ` ), and ids as seen in the parseable or json
72
+ output of ` npm token list ` . This will NOT accept the truncated token
73
+ found in the normal ` npm token list ` output.
0 commit comments