Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
11-05-2019 03:06 AM - last edited on 11-26-2019 01:50 PM by Ryan.Paredez
Hello,
I am trying to connect to the controller from the agent.
However what is the account access key? I didn't receive it by email. I tried using the account name but am receiving an error
Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at the computer account (system) level.
Thx
Solved! Go to Solution.
11-06-2019 09:21 AM
The account access key can be found on your Controller via the License Management section. To check what it is go to your Controller GUI, log in, and then click on the cog wheel in the top right-hand corner and then go to License. Once there, then click on the "Account" tab, and then you'll see a hyperlink next to account which will say "show." Click on "show" and you'll get the acess key the controller-info.xml file is expecting, and your account name too, i.e. customer1.
10-16-2023 01:17 AM
Hi @Eric.Miller ,
Can we get this account acces key using any API command instead of getting it from the controller?
Regards,
Mohammed Saad
10-16-2023 09:55 AM
Since this post is from 2019, it's unlikely to get a reply. I would suggest you re-ask this question on the forums so it gets more visibility from the community.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form