KB Article Number is KA355040.
CLM Version: 2.x
The below error is thrown while logging on to the Cloud Admin Console.
call: getListEntryWithFields(), TableName: Location, Class:com.bmc.cloud.model.beans.Location. Server response authenticity for login type IMPERSONATE cannot be validated (ARERR 219009)
Cloud Admin Console will fail with IMPERSONATE error if there are any issues while authenticating the user. In this case, the Super user password doesn't match between Platform Manager and Cloud Portal.
While installing Platform Manager through Install Planner (IP), the IP will ask for Super user password. This will be encrypted and stored in the \Program Files\BMC Software\BMCCloudLifecycleManagement\Platform Manager\Configuration\Cloudservices.json file on the Platform Manager server.
Super User Password AccessAttribute in Cloudservices.json file:
"attributeValue" : "XXXXXXXXXXXXXXXXXXXX==",
"description" : "Super User Password",
The IP will also ask for the Super user password while installing Cloud Portal on the Enterprise AR Server. This password should be same as the one given while installing Platform Manager. If there is a mismatch, then the Cloud Admin Console will fail with IMPERSONATE error. The Super user password specified while installing Cloud Portal is encrypted and stored in CMF:PluginConfiguration form on Enterprise AR Server. Please contact BMC Support if you need help to determine if the password is valid in the AR form and in the above entry.
Similiarly, there is a section which mentioned the hostname,port,username,password of the CloudDB machine. This appears TWICE in the file.
You can seach this section by "description" : "Database(AR) Server", Ensure all the entries here are correct in both the sections.
Also, please refer to KA354652 / Cloud Portal fails with ARERR 219009 for Cloud Admin and Cloud end users.
I experienced this same exact error after adding a user... as it turns out the platform manager cache needed to be cleared.
1. Stop the BMC CSM Service on the platform manager server.
2. Navigate to C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager or wherever you've installed it and remove, or rename the cache directory.
3. Restart the BMC CSM Service.
If you receive the "No Services Registry", or something similar... give the PM some more time to finish restarting.
I just went through this exact error. Please check the Enterprise AR to see that fixed licenses are in place. Then check the Cloud AR and see if fixed licenses are in place. You need to ensure that AR User Fixed Licenses exist on both servers in the same quantity.
Before I found this I created a user in E-AR to see that it got DSO'ed over to C-AR. This user had no permission groups associated with Cloud. DSO was validated as successful. I then created the clmadmin user and added the groups required. Went to C-AR and nothing was DSO'ed.
I then added AR User fixed licenses to the C-AR (in my case I added 15). I restarted the Platform Manager and made a change to the clmadmin user on E-AR and this time the DSO worked correctly. I am not sure if it is a bug with Install Planner but for some reason the licenses did not get put on C-AR during the installation.