In the OutSystems platform, an API is consumed from an external system which was working fine in the beginning (like to say it was first consumed in sept 2024 till last week). However, in the Dev and TST environments, we are encountering the following errors when attempting to connect to the API domain:
Interestingly, the same API call works as expected when tested through Postman, and the response is received successfully.
Seeking guidance on how to resolve this SSL/TLS trust issue within the OutSystems environment.
Hi,
The call to your API is from OutSystems server side. This call is https, so the communication between OutSystems server and your API must be secure. This communication is secure if the SSL certificate of your API is valid and not expired. Surely the SSL certificate is expired if you could connect in sept 2024. Can you validate the expiration?
In Postman your "enable SSL certificate verification" setting is off, so there is not any SSL verification.
Kind regards, David.
Server hosting your Dev and TST environments doesn't trust the API’s SSL certificate anymore — maybe it’s new, changed, or missing a root or intermediate certificate. To fix it, open the API link in a browser, export the certificate chain, and install those certificates into the Windows server where Dev and TST run. Put the root certificate in the Trusted Root store and the intermediate one in the Intermediate store.
Once that’s done, restart the server or services, and your API should work again — just like before.
@Mary M J : You mentioned that "The remote certificate is invalid according to the validation procedure." This indicates that the certificate installed on the external system has an issue. The possible reasons could be that the certificate has expired, the certificate chain is incomplete due to a missing intermediate certificate, or the certificate is self-signed. To resolve this issue, you have two options: either fix the certificate on the external server by renewing it, completing the chain, or using a valid certificate from a trusted authority, or trust the certificate on your OutSystems servers (only if it is an on-premises installation) by manually adding the certificate to the trusted store.
The issue is resolved now. It was indeed problem with the API server certificate. Thanks all for your help.