How to minimally test IMG WebService commands in RSA IMG
Originally Published: 2015-03-16
Last Modified: 2023-09-25
Article Number
Applies To
Issue
Resolution
From the above
click the On radio button for field 'Web Services Interface:'
define any IP addresses which you wish to restrict WebServices requests in the field enabled 'IPs allowed to sent/invoke web services:'
for the purpose of this article it is not necessary to define the 'Import Directory:'
For Google Chrome install the Application from the Chrome Webstore named Advanced Rest Client
For Mozilla Firefox install the Firefox Add-on name named RestClient
Both will allow for a Rest Client to be run from a browser and both are similar in functionality.
For example, from within Google Chrome, in the URL field if one enters 'chrome://extensions/', this will return all Chrome Extensions of which you should see an entry named 'Advanced Rest Client', as evidence:
Clicking the Options link below the 'Advanced REST Client' will open the application which should appear similar to
If your display is not similar to the above you may need to click on the first menu choice entitled 'Request' on the left hand.
From here one can submit a WebService Request to the IMG API and see the return response.
The fields you will need to define are as follows (listed in top down order):
URL: This should be the URL for the Identity Management and Governance URL for example, if your current Identity Management and Governance application is reachable at https://img-dev/aveksa/main then the URL would be defined as https://img-dev/aveksa/command.submit?cmd=<WebService command name>
replacing <WebService command name> with its actual value, for example findApplications
Define the appropriate radio button for whether the request is a GET or POST method. The online documentation in IMG at menu choice Admin / WebServices and clicking the down arrow chevron
If the command is a POST command the XML to pass will need to be defined in the 2nd text box below the radio buttons and the Content-type will need to be defined as Application/XML from the drop down, for example
Below is an example of a completed WebService request for 'findApplications' and parameters of name=Bugzilla and returnColumns=short_desc
From the above the Status Code of 200 indicates a successful submission. Typically when a request is improperly submitted the Status will be in the 4xx range.
The bottom text box display the output of the command of which we see the return value for findApplications?name=Bugzilla&returnColumns=short_desc is short_desc=Tooltip for Bugzilla
Related Articles
High CPU utilization caused by Webservice calls embedded in request forms in RSA Governance & Lifecycle 49Number of Views Generic REST Collector fails with GENERIC_REST_EXCEPTION_NULL_API_URL error when calling the Group Data operation in RSA I… 137Number of Views IDC unification runs into an error called by by webservice call in RSA Identity Governance & Lifecycle 26Number of Views Error "No such file or directory while trying to open /dev/disk/by-id/scsi-XXXX-part1" and services do not start on RSA Se… 62Number of Views RSA Identity Management and Governance DB logs, task results, task progress are not available on run details of collection… 128Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?