token: use figgy-config to make sure extra opts are there by zkat · Pull Request #149 · npm/cli

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat · 2019-01-28T23:39:18Z

This fixes a reversion reported by @evilpacket and co, where we weren't sending some metadata and auth info on npm token ls. This has to do with the npm@6.6.0 rework.

aeschright

⭐️

alexsasharegan · 2019-02-05T17:56:23Z

Will this also resolve what looks like the same issue with the token subcommand? This output immediately follows a successful login. Of note, I do use TOTP 2FA.

$ npm token create --read-only
npm password: npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

/home/alex/.npm/_logs/2019-02-05T17_41_20_882Z-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'token',
1 verbose cli 'create',
1 verbose cli '--read-only' ]
2 info using npm@6.7.0
3 info using node@v10.15.1
4 verbose config Skipping project config: /home/alex/.npmrc. (matches userconfig)
5 info token creating
6 verbose stack Error: Unable to authenticate, need: Basic, Bearer
6 verbose stack at res.buffer.catch.then.body (/home/alex/.npm-global/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
6 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
7 verbose statusCode 401
8 verbose cwd /home/alex/github.com/pictalk/pictalk
9 verbose Linux 4.18.0-13-generic
10 verbose argv "/usr/bin/node" "/usr/bin/npm" "token" "create" "--read-only"
11 verbose node v10.15.1
12 verbose npm v6.7.0
13 error code E401
14 error Unable to authenticate, your authentication token seems to be invalid.
15 error To correct this please trying logging in again with:
15 error npm login
16 verbose exit [ 1, true ]

@zkat

PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

zkat added the semver:patch semver patch level for changes label Jan 28, 2019

zkat requested a review from a team as a code owner January 28, 2019 23:39

token: use figgy-config to make sure extra opts are there
b61b8a1

zkat force-pushed the zkat/fix-token branch from 2312376 to b61b8a1Compare January 29, 2019 00:08

aeschright approved these changes Jan 30, 2019
View reviewed changes

aeschright merged commit ce2c4bd into release-nextJan 30, 2019

aeschright deleted the zkat/fix-token branch January 30, 2019 00:02

aeschright pushed a commit that referenced this pull request Feb 14, 2019
token: use figgy-config to make sure extra opts are there (#149)
4cf850d
PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright

kevinjm39 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities kevinjm39/cli#16
Open

CALISOULB mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#19
Open

varmakarthik12 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#30
Closed

bumplzz69 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities bumplzz69/cli#38
Open

mtdev2 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities mtdev2/cli#91
Open

Bhanditz mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities Bhanditz/cli#29
Open

baby636 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities baby636/cli#62
Open

LadyK-21 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities LadyK-21/cli#26
Open

adamlaska mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities adamlaska/cli-3#22
Open

snyk-ioBot mentioned this pull request Oct 22, 2024
[Snyk] Fix for 21 vulnerabilities Graybar-codespace/cli-3#100
Open

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 3, 2026
🤖 봇 응답 (npm#149)
2e4c740

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 8, 2026
📊 대시보드 데이터 업데이트 (npm#149)
9006beb

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 19, 2026
🔧 자동 수리 완료 (npm#149)
0a204e2

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 12, 2026
🔥 트렌드 선점 후보 갱신 (npm#149)
a688362