When integrating with external systems such as, for example, consuming webservices, integrating with external databases or with an Active Directory, there is often the requirement to do so over HTTPS.
When those external servers possess an SSL certificate issued by a public certificate authority (CA), the HTTPS connection is successfully established without the need for further configuration.
Applicable use case
It may be the case that those external servers bear certificates that are not signed by a public CA, namely self-signed certificates.
These certificates are not trusted by the client servers (in this case, the OutSystems servers), and therefore need to be added to their trusted root store. When that step is not executed, it will lead to errors such as the ones listed in this article.
For OutSystems PaaS environments, this operation will need to be performed by OutSystems support. This option is available depending on your subscription, check more details at Cloud service delivery requiring direct assistance from OutSystems Support.
Requesting the service
In order to do this on the OutSystems PaaS you’ll need to open a support case and:
- Provide the certificate, in .CER format
- Make sure to be clear about what environments should the certificate be installed
What will OutSystems deliver
OutSystems staff will install the certificates in all the necessary front ends and notify you once the operation is complete.
Please note that OutSystems does not monitor your certificates expiration date. Make sure to request this service ahead of time, taking into account the SLA for this service.