feat: separate login/adduser, remove auth types #5550
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: This removes all
auth-type
configs exceptweb
andlegacy
.BREAKING CHANGE: Finally,
login
andadduser
are now separatecommands that send different data to the registry.
BREAKING CHANGE:
auth-type
config valuesweb
andlegacy
only trytheir respective methods, npm no longer tries them all and waits to see
which one doesn't fail.
The difference between
adduser
andlogin
depends on theauth-type
.web
: the POST to/-/v1/login
contains a{ create: true }
valuein its payload for
adduser
legacy
thePUT
request to/-/user/org.couchdb.user:${username}
contains an
email
value in its payload foradduser
.