/
SWS SaaS Configuration Guide

SWS SaaS Configuration Guide

Introduction


SWS SaaS service requires no installation.

Each customer has a dedicated endpoint to sign documents.

The customer can choose a specific performance class based on bandwidth and throughput (contact a sales account in order to know the classes and related rates).


Configuration


SWS SaaS requires a specific SSL CCA certificate to establish secure connection between your client application and your dedicated virtual host.

You can find an example of FQDN below:

sws-COMPANYNAMEsaas.test.namirialtsp.com

where COMPANYNAME will be replaced with your company name.


If you want to use the SOAP interface then the signing endpoint will be:

https://sws-COMPANYNAMEsaas.test.namirialtsp.com/SignEngineWeb/sign-service

If you want to use the REST interface then the signing endpoint will be:

https://sws-COMPANYNAMEsaas.test.namirialtsp.com/SignEngineWeb/rest/sign

The SSL CCA certificate is delivered by mail in a zip protected by password.

This password is delivered by SMS to the customer.

You can find how to configure SSL certificate on SoapUI at this link.

You can find how to configure SSL certificate on Postman at this link.

Related content

Configure Soap UI
Configure Soap UI
More like this
SWS Integration Guide
SWS Integration Guide
More like this
Standard interface
Standard interface
More like this
Configure Postman
Configure Postman
More like this
SWS Description
SWS Description
Read with this
SWS OnPremise - Standalone
SWS OnPremise - Standalone
More like this