Affects Version/s: 6.3.0
Fix Version/s: None
When setting NPM remote repository with an NPM registry that requires remote authentication, the test button will successfully test the user and pass authentication against the NPM registry at initial stage but after saving the configuration and returning to the page of the created remote repository the test button will return 401 error due to the change of the plain text password to encrypted one.
Steps to Reproduce:
1 - Create a new remote repository with remote authentication.
2 - Test the authentication (expect successful connection) and save the configuration.
3 - Navigate to the remote repository created in step #2 and notice that when clicking test button again, this time 401 will be returned.
4 - Check the remote authentication and the password will be changed to encrypted and not plain-text as it used to be.
Please note that this is a UI test and does not affect the functionality of the NPM remote repository.