@JayBR , thanks for the post, and welcome to our community!
I was able to find 2 incidents with this error……and only 1 was actually solved.
Here’s the case resolution (copied and pasted so ), which I hope applies to you!
Note, I replaced the password the customer provided but the effect is clear).
We found the issue. Customer was using the base64 password encoded by the commandline centOS.
Commvault API requires base64 encoded password hash. Recommended customer use online tool (https://www.base64encode.org/) which generates the correct one, but the command line at centOS does not. The difference is only one character at the end.
Customer provided example:
Example password: "<password removed>"
online tool's encoded: U3R1cGlkQ3VzdG9tZXI2NjY=
centOS encoded: U3R1cGlkQ3VzdG9tZXI2NjYK
@JayBR no need for an additional setting what so ever. I assume you remove the {{ }} brackets signs e.g. replace them with your username and base64 encoded password without the brackets.
@Mike Struening , thanks for your answer, it turns out it was exactly that. The Base64 hash encoded password was generated by a command line tool and some characters were missing. We’re good to go. Best regards!