Join the Conversation
- Find Answers
- :
- Splunk Products
- :
- Splunk AppDynamics
- :
- Re: API Problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
