In an environment with FIPS 140-2 compliance settings enabled in Active Directory (the Active Roles service account and/or proxy account has This Account supports Kerberos 128 bit encryption and This account supports Kerberos AES 256 bit encryption enabled on the Account tab for the Active Directory User object), attempting to connect to the service using the Connect-QADService -proxy cmdlet fails with the error:
Security verification was not successful for the received data.
Attempting to connect using the Active Roles Console from the same client machine also fails the error:
The user name or password is incorrect.
Attempting to connect using the Active Roles Management Shell or the Active Roles Console from the Active Roles Administration Service host server is successful.