| Table of Contents |
|---|
Introduction
SWS SaaS like every SaaS service not require service requires no installation. Every
Each customer will have has a dedicated endpoint to make a signatures.sign documents.
The customer can choose a specific performance class SWS SaaS is offered with difference types based on bandwidth and throughput (contact a sales account in order to know the classes and related rates).
Configuration
SWS SaaS require requires a specific SSL CCA certificate to establish secure connection between your client application and your dedicated endpoint. For example the dedicated enpoint will bevirtual host.
You can find an example of FQDN below:
| Code Block |
|---|
sws-COMPANYNAMEsaas.test.namirialtsp.com |
Where where COMPANYNAME will be replaced with your company name, if you dedice .
If you want to use the SOAP services, the full address interface then the signing endpoint will be:
| Code Block |
|---|
https://sws-COMPANYNAMEsaas-test.namirialtsp.com/SignEngineWeb/sign-service?wsdl |
If you want to use the REST interface then the signing endpoint will be:
| Code Block |
|---|
https://sws-COMPANYNAMEsaas-test.namirialtsp.com/SignEngineWeb/rest/sign |
The SSL CCA While the SSL certificate is delivered by mail in a zip protected by password, and for SMS will receive the zip 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 linkAt this step 6 of this link is descrided how configure SSL certificate with SoapUI, while at this link is describe how configure SSL with Postman.