During configuration and testing of the vSphere Authentication Proxy we discovered some problems that make the use of the Authentication Proxy very unreliable within multi Domain Controller environments. In our case we are using the Authentication Proxy in conjunction with vSphere Auto Deploy but the problem also occurs in scenario’s without Auto Deploy.
While troubleshooting the vSphere Authentication Proxy (vSphere 5.1) I ran into a bug which will I highlight in this article. After successfully installing the Authentication Proxy I discovered an error message in the C:\ProgramData\VMware\vSphere Authentication Proxy\logs\camadapter.log: 2012-xx-xx 14:03:35: Failed to bind CAM website with CTL 2012-xx-xx 14:03:35: Failed to initialize CAMAdapter.
I recently had some issues getting the vSphere Authentication Proxy Plug-in to be enabled within vCenter Server 5.1. This is the error message that was displayed: “The server could not interpret the client’s request. (The remote server returned an error: (404) Not Found.)”