We have a policy in place that requires "complex" passwords for service accounts. So our AD Admins created a service account password that was randomly generated and set/working for our "shell" based provisioning scripts that we use for spacewalk.

When we attempted to use it with Foreman, it failed to authenticate: https://www.dropbox.com/s/6jobrv6041jm55a/Screenshot%202015-09-25%2010.22.28.png?dl=0

I am not sure exactly what part is failing because passwords are obfuscated in logs (which is a good thing) :)

Here is the password (which we are no longer using) that caused the problem:

'LLunwoDu5,9zziZ04H`N63E;wuHes5gTK8`Du8xDuB0CpCwV$PHyvzY

I also tried simpler passwords with each of the following:

• single quote - doesn't seem to affect it whether its in the middle or at the beginning
• commas - no effect
• backticks - don't seem to have any effect
• semi-colon - no effect
• dollarsign - no effect

SO...

It has something to do with a combination of those, or maybe that particular combination? Either way, it seems a bit strange. For what its worth, we are using Active Directory authentication on vCenter, but I don't think that has anything to do with it. Also, as I stated above, I can use that obnoxious password to authenticate from our shell scripts that use the VMware Perl SDK, so I don't think its a VMWare issue.

I found this in 1.9.0, and confirmed it still exists in 1.9.2