Excerpt | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Testing with SOAP UITesting without a signed keyA normal „serviceCheck“ request for an instance “Cortex” is configured the following way.
The related SOAP UI request looks like this.
Testingwith signed keyWe have developed a small tool, “KGS Security Key generator” which generates a signed text which can be used together with SOAP UI. We will use the instance “Cortex” as our example. The installation package contains both a private keystore and public keystore for testing. The “private” keystore contains a keypair consisting of both private and public key whereas the “public” keystore consists of certificate with public key. In case of testing with SOAP UI, you need the file private (keystore) located at “security_testing/keystore” and public (keystore) located at “security_test-ing/keystore”.
| WebService MainConfiguration | Opened “Cortex” configuration | Screenshot of “KGS Security Key generator” | Display of signed text. | Screenshot of SOAP UI with added seckey | Screenshot of ServiceCheck result |
Highlighted Plus-button in SOAP UI | ||
---|---|---|
Locate your attachment and attach it.
Click on the ‘Part’ box as shown below.
Highlighted “Part”-column in SOAP UI | ||
---|---|---|
Select the name of the attachment as shown below.
Selected attachment in SOAP UI | ||
---|---|---|
At this point, your attachment along with your create request is ready.
...