Hello Leonardo
We updated OutSystems Now a couple of weeks ago with some security improvements. One of those improvements was related to certificates. Until that update, OutSystems Now already worked with HTTPS but it allowed invalid certificates to be used. With the update, we enforced only valid certificates.
However, we realized that some customers would have issues with this approach, mainly in development environments where it's common not to have valid certificates. To address this, we launched another version with the option to accept invalid certificates at the user's risk. This behavior is very similar to what most browsers do nowadays (ask the user to continue because the certificate is not valid).
Although it's now possible again to use invalid certificates, we do recommend the usage of a valid certificate as a best practice. Please confirm that you have the latest version of OutSystems Now.
Thanks in advance
We updated OutSystems Now a couple of weeks ago with some security improvements. One of those improvements was related to certificates. Until that update, OutSystems Now already worked with HTTPS but it allowed invalid certificates to be used. With the update, we enforced only valid certificates.
However, we realized that some customers would have issues with this approach, mainly in development environments where it's common not to have valid certificates. To address this, we launched another version with the option to accept invalid certificates at the user's risk. This behavior is very similar to what most browsers do nowadays (ask the user to continue because the certificate is not valid).
Although it's now possible again to use invalid certificates, we do recommend the usage of a valid certificate as a best practice. Please confirm that you have the latest version of OutSystems Now.
Thanks in advance