Liferay PaaS: Custom domains are not SSL certified by Liferay

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• We have domains that are NOT using custom SSL certificates, however, they refuse to use https connection.

Environment

• Liferay PaaS

Resolution

• The correct methodology to achieve these results is modifying your LCP.json file of your Webserver service like the following:

• "prd": {
        "loadBalancer": {
          "targetPort": 80,
          "cdn": true,
          "certs": [
            {
              "customDomains": ["custom-domain.with-custom-certificate.example"],
              "key": "@ssl-key-secret-multidomain",
              "crt": "@ssl-crt-secret-multidomain"
            },
            {
              "customDomains": ["custom-domain.with-default-certificate.example"]
            }
          ]
        }

• Proper changes in certificate generation may take a couple of hours.

Additional Information

• Adding a Custom Domain via LCP.json
• Please note, that in extreme conditions, certification process can take up to 24–48 hours.