Closed
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
If you have a custom registry that authenticates clients via mTLS (i.e. client cert/key in your .npmrc), you cannot publish unless you also specify some credentials, due to this check.
If your registry also validates any provided Authorization headers, the publish may fail if the credentials are invalid. Depending on the registry, this may not be configurable, so you might need to doubly authenticate (mTLS AND credentials).
Expected Behavior
npm publish with just a cert + key should proceed past this check.
If this gets fixed, future work for npm/npm-registry-fetch#38 should also take it into account.
Steps To Reproduce
No response
Environment
No response