Configure Postman

Prerequisites

1. SWS Postman collection: collection download
2. SWS Postman collection example files: files_for_example 
3. Postman (https://www.postman.com/downloads/)

Importing collection

Once collection is downloaded then import the collection inside your Postman app.

Go to "Collections"

→ "Import" → "File"→ "choose the collection previously downloaded"

After choosing the file from your download directory you must see something like this:

Choose "Import" , if everything was successful a new collection must be created inside your workspace and message like this appears inside the screen:

Additional configurations

Configure baseUrl on collection global variables

All the requests inside the collection are parametrized using the variable {{baseUrl}} inside request urls so change it to point to your domain

NOTE: if you are testing the TEST SWS SaasS the "baseUrl" is:

https://sws-companynamesaas.test.namirialtsp.com/SignEngineWeb

While the p12/jks can be downloaded at this link

Check files inside your workspace

Before sending the first requests check that files inside body requests are correctly configured with your environement if not try to reload files from your file system, because when importing SWS collection all file location link has to be reconfigured.

Configure auth certificates inside Postman (optional)

Goto "File" → "Settings" → Certificates

Choose "Client Certificates" → "Add Certificate"

Configure your endpoint address and your PFX file with your passphrase than click "Add"

NOTE: pay attention that postman does not support JKS format.

Once completed you should see something like this:

Configure Client SSL certicates when use SWS SaaS environment (optional)

When you have a SWS SaaS based solution, then you must configure client ssl certificate agaist your production fqdn (sws-<your_company_name>saas.namirialtsp.com). See also: Configure Postman#ConfigureauthcertificatesinsidePostman(optional)