Splunk AppDynamics

API Problem

CommunityUser
Splunk Employee
Splunk Employee

I have upgraded to 4.3 last week for our on premise environment. Since the update I have been unable to access the REST URL from the metric browser. It returns a 403 Access Forbidden error. I have also been unable to use a curl command such as curl -i --user c***@customer1:****https://appdynamics.******.com/controller/rest/applications/SvcMgmt-Remedy9-Prod/metric-data?metric-.... It did work a couple days ago but then it failed again.

Does anyone have any suggestions about how to fix this? 

Thanks 

Labels (3)
0 Karma
1 Solution

Pratik_Maskey
Communicator

Hello Wesley,

Are you trying the REST API on the same browser where you have logged in to your controller?
If yes, then it will not work because since 4.3.3 we have implemented anti-CSRF token to prevent cross site vulnerabilities. It means alone jsessionID is not sufficient and it requires CSRF token as well which is not passed along if your are using the same browser session you logged into your SaaS controller.

You can do the following:

1) Either use a REST client where you can enter the username/password in the format username = <username>@<account-name> and password.
OR
2) Open a new browser or incognito mode to try the same URL and it will prompt you to enter the username and password.
Remember username is always <username>@<account-name>

Regards,

Pratik

View solution in original post

0 Karma

Pratik_Maskey
Communicator

Hello Wesley,

Are you trying the REST API on the same browser where you have logged in to your controller?
If yes, then it will not work because since 4.3.3 we have implemented anti-CSRF token to prevent cross site vulnerabilities. It means alone jsessionID is not sufficient and it requires CSRF token as well which is not passed along if your are using the same browser session you logged into your SaaS controller.

You can do the following:

1) Either use a REST client where you can enter the username/password in the format username = <username>@<account-name> and password.
OR
2) Open a new browser or incognito mode to try the same URL and it will prompt you to enter the username and password.
Remember username is always <username>@<account-name>

Regards,

Pratik

0 Karma

Abhilash_C
Explorer

Hi Pratik,

Thanks For your Valuable Reply. It worked for me as you suggested but it Didn't Returned any XML output ? It Just Returned

<metric-datas/>

Do we need to configure something to access this Rest API ? Please help me 

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...