chore: remove auth-always (#4921)

* chore: remove auth-always

* npmrc

* revert yarn1

.npmrc

@@ -1,2 +1 @@
-always-auth = true
 fetch-retries="10"

website/blog/2019-10-05-verdaccio-4-with-ldap-and-docker.md

@@ -442,6 +442,4 @@ This is due to wrong permissions or ownership in `storage` directory, dont forge
 
 - When should I use `--always-auth` when running `--add-user`?
 
-If you keep having `403` issues when retrieving packages from the registry, and permissions and ownership have been fixed, we have found that adding `--always-auth` will solve the issue.
-
-In my case, I have found that `--always-auth` was required in my production environment.
+Since npm 7.10, the config option `always-auth` has no effect. You can safely remove it from your configuration.

website/docs/how-to-deploy-on-AWS.md

@@ -94,8 +94,6 @@ To make Verdaccio launch on startup, run the commands below:
 
 **Step 10:** Registering a user in verdaccio registry
 
-` npm set always-auth true`
-
 ` npm adduser`
 
 It will ask for username, password and valid email id to be entered. Make a note of this details that will use later to login in verdaccio registry to publish our library.

website/docs/packages.md

@@ -77,11 +77,7 @@ npm ERR!     /Users/user/.npm/_logs/2017-07-02T12_20_14_834Z-debug.log
 
 You can change the existing behaviour using a different plugin authentication. `verdaccio` just checks whether the user that tried to access or publish a specific package belongs to the right group.
 
-Please note that if you set the `access` permission of a package to something that requires Verdaccio to check your identity, for example `$authenticated`, npm does not send your access key by default when fetching packages. This means all requests for downloading packages will be rejected as they are made anonymously even if you have logged in. To make npm include you access key with all requests, you should set the [always-auth](https://docs.npmjs.com/cli/v7/using-npm/config#always-auth) npm setting to true on any client machines. This can be accomplished by running:
-
-```bash
-$ npm config set always-auth=true
-```
+Note: Since npm 7.10, the config option `always-auth` has no effect. You can safely remove it from your configuration.
 
 #### Set multiple groups {#set-multiple-groups}
 

website/versioned_docs/version-6.x/how-to-deploy-on-AWS.md

@@ -94,8 +94,6 @@ To make Verdaccio launch on startup, run the commands below:
 
 **Step 10:** Registering a user in verdaccio registry
 
-` npm set always-auth true`
-
 ` npm adduser`
 
 It will ask for username, password and valid email id to be entered. Make a note of this details that will use later to login in verdaccio registry to publish our library.

website/versioned_docs/version-6.x/packages.md

@@ -77,11 +77,7 @@ npm ERR!     /Users/user/.npm/_logs/2017-07-02T12_20_14_834Z-debug.log
 
 You can change the existing behaviour using a different plugin authentication. `verdaccio` just checks whether the user that tried to access or publish a specific package belongs to the right group.
 
-Please note that if you set the `access` permission of a package to something that requires Verdaccio to check your identity, for example `$authenticated`, npm does not send your access key by default when fetching packages. This means all requests for downloading packages will be rejected as they are made anonymously even if you have logged in. To make npm include you access key with all requests, you should set the [always-auth](https://docs.npmjs.com/cli/v7/using-npm/config#always-auth) npm setting to true on any client machines. This can be accomplished by running:
-
-```bash
-$ npm config set always-auth=true
-```
+Note: Since npm 7.10, the config option `always-auth` has no effect. You can safely remove it from your configuration.
 
 #### Set multiple groups {#set-multiple-groups}