To work around this issue, follow the steps outlined below. Essentially, you will be changing the EUM key within the events-service-api-store.properties file temporarily so that EUM can fail authorization again. Once the EUM Server fails, you will change the EUM key back to the original value, at which point the EUM Server should successfully connect.
Please note that the paths to the platform components in the commands below will need review to ensure accuracy.
1.Please stop your EUM Server manually. Once the EUM Server is stopped, use your Platform Admin CLI to stop the Events Service (ES) cluster.
3.Update the events-service-api-store.properties file (not.orig) on each of the ES nodes, changing the last character in ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea60. For example:ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea6a.
On Events Service Nodes:
sed -i 's/6a981b83-251d-4d0b-a56a-b309fc3bea60/6a981b83-251d-4d0b-a56a-b309fc3bea6a/g' /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties
4.Using your Platform Admin CLI, start the Events Service cluster. Once the ES cluster is running, start your EUM Server manually.
6.Update the events-service-api-store.properties file on each of the ES nodes, changing the last character in ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea6a back to the original value. For example: ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea60.
At this point, the Events Service nodes will be configured with the original EUM key and the EUM Server should successfully connect to the Events Service. Please contact AppDynamics Support if you continue to encounter issues.