I was able to get it working with Postman. Here are the steps that I performed.
First off, I assume you acquired an authorization token. If not, do that.
Once the authorization token is acquired, add it as a header with the following format:
Key = Authorization
Value = authToken <AUTHORIZATION_TOKEN>
If you are not using a secure connection on your Presentation Server (ex. https), the GET URI example is the following:
If you are using a secure connection on your Presentation Server (ex. https), the GET URI example is the following:
These also assume you are using the default ports (http:80; https:443). If you are not using the default ports, then you will need to change the Presentation Server portion to the following: http(s)://<PRESENTATION_SERVER>:<PORT>/.
Let me know if you have any questions and whether this works for you or not...
Yes, I already have my auth token, but it is acting like that URL does not exist. We're using a load balancer, so there is no port. Let me check with those guys on this. Perhaps they only are forwarding requests on to a specific path for some reason. I'll check on that.
Hey Michael... Any luck?
No luck yet.
Michael, did you check TSPS logs for any errors just after sending the API?
Are you seeing this error "CSRF Filter - Header Referer is not matched. Blocking " in the TrueSight.log file? If so, you may try to apply Knowledge Article 000147410 (KnowledgeArticle - BMC )
No errors in the logs at all. In fact no entry in the logs at all even when I try to connect. This tells me that perhaps it's not even getting past the load balancer.
Did you try skipping the LB and put the active TSPS hostname in the URL?
If you get confirmed by your LB admins that issue is not there, then the best would be you raise a support case to troubleshoot it.