You can use this connector to test REST or SOAP services. It is a generic connector where you can specify a URL to send data such as Query String, Form data, or Payload Data, and get a response. You can then compare the response with any string that would indicate success.
The HTTP connector consists of the following authentication types:
Basic Auth:
If you provide values for the Basic Auth User and Password when setting up the connection, two auth headers are sent with the request.
Authorization: Basic <base64 encoded username:password>
RESTAuthorization: <base64 encoded username:password>
OAuth2 (limited support):
If you provide a value for the Access Token URL, an OAuth2 token will be retrieved from the specified URL before the request, then the following auth header will be sent with the request.
Authorization: Bearer <access token>
Request Params are used to configure the OAuth2 authorization. Supported values are:
grant_type = password or client_credentials
client_id = provided by the OAuth2 IDP when registering the client.
client_secret = the secret associated with the client_id
When the “password” grant type is used, Username and Password are required.
Hover over the field labels for additional help.
Listener to receive data from the Subscriber channel of the SOAP driver:
Currently the connector does not provide a listener. You may consider using SoapUI which does provide a listener.
The connector work with RBPM REST calls:
See the following explanation of possible issues that may be encountered.
Authentication is done using the RESTAuthorization header which is supplied automatically by the HTTP connector. Enter the username, and NOT an LDAP DN, and the password in the connection properties. Don't use Italics. Check the guide when Italics is used and change all instances of Italics to normal text or whatever is applicable.
In many RBPM REST calls it requires a header value of:
Accept: application/json
Otherwise it returns error: 415 unsupported media type.
Usage of the URL suffix field: The value of this field is appended to the URL specified in the connection. With it you can add whatever URL suffix is required for the specific test, including a query string.
NOTE:No part of the URL is encoded automatically. If the URL or Suffix do not work, you have to manually encode them. See http://www.w3schools.com/tags/ref_urlencode.asp. You may replace spaces with a + sign if the space is in the query string.
Specify header data: Specify the key/value pairs in the Header Data table within the action.
Specifying form data: Specify the key/value pairs in the Form Data table within the action. Note that this is only applicable for the POST method action.
Using header data, form data, and normal payload raw data together by HTTP call: Form data and payload raw data are mutually exclusive and cannot be used together. If both are included in an action, the raw data will be ignored.
Using with SOAP Web Services: The SOAP is about sending the right SOAP document (XML) as raw payload data. Authentication can be tricky and may not be possible in this connector depending on the SOAP service you are using. Paste your SOAP doc in the Raw Data field.
Expected Results field: If you leave it blank the action always succeeds because it always matches nothing). You can specify any string in this field that may be returned from the server and the action will succeed. If you use RegEx, you can enter a regular expression in the Expected Results tab.
Start a UserApp workflow using the HTTP connector: You can, but you will want to try the User App connector first to be sure it will fit your needs. If you need to do it manually, you can use the RBPM REST services (discussed in an earlier paragraph).