Prior to configuring and testing your application that will invoke web service requests, Verato recommends testing connectivity using a basic tool such as SoapUI as a first test, just to ensure that the certificates and passwords are working as expected and IP addresses are correctly added to an allowed list. This helps ensure that any future connectivity issues can be debugged knowing that the neither the certificates, passwords, nor IP addresses are the cause of the connectivity issue.
To perform a basic connectivity test using SoapUI:
The specifics may vary based on the version of SoapUI.
- First send to Verato your IP address from which the web service request will originate—we will add the IP address to an allow list.
- In SoapUI, click File and then select New SOAP Project to create a new project.
- SoapUI prompts you for the Initial WSDL. Browse and select the WSDL provided by Verato.
- Create a new Request in SoapUI.
- Next set the preferences to point SoapUI at the correct client certificate. Click the File menu, select Preferences. This opens a new window. In the new window, enter the KeyStore and KeyStore Password.
- For KeyStore, click Browse next to KeyStore and browse to select the *.jks file provided ahead of time by Verato.
- For KeyStore Password, type in the certificate password provided by Verato that corresponds to the *.jks file.
- Click OK to close the preferences window.
- Next set the username and password that will be used to authenticate to Verato’s product. This is a username and password provided to you separately from Verato (not the same password as the one for your *.jks certificate). In the lower-left corner of SoapUI, you will find a window for Request Properties.
- Click the green triangle icon in the upper left corner of the Request window to execute the web service request.
- The empty box on the right side of the Request window is populated with the web service response.
The web service response shown above indicates a successful connectivity test. The web service request made it to Verato, the client and server were able to complete their handshake to confirm they trust each other, and the web service request was successfully authenticated in Verato’s software. The query was looking for one or more fictitious identities that do not exist in the Reference Database, so the query response indicates that the web service completed successfully, but with an outcome that the entity you are looking for does not exist.