Enable HTTPS
Put a valid TLS certificate in front of OpenIAM and serve the portals over HTTPS.
Goal: OpenIAM served over HTTPS with your real certificate. Time: 15–20 minutes. Prerequisites: install complete; certificate, private key, and CA bundle for your OpenIAM DNS name on hand.
Do this now rather than later: the first-login flow asks whether the application supports SSL, and SAML federation with Microsoft Entra requires HTTPS (and fails confusingly without it).
Don't have a certificate yet? Three lab-friendly options
Let's Encrypt
Host has a public DNS name and port 80 reachable from the internet
sudo dnf install certbot && sudo systemctl stop httpd && sudo certbot certonly --standalone -d openiam.poc.example.com && sudo systemctl start httpd — standalone mode needs port 80, which Apache is holding, hence the stop/start. Cert lands in /etc/letsencrypt/live/<name>/ (use fullchain.pem and privkey.pem in step 2)
Internal CA
Your org runs AD CS or another internal CA
Issue a web-server cert for the DNS name; fine for the lifecycle POC and internal SSO — browsers inside your org trust it
Self-signed
Nothing else available
Works for the lifecycle POC only; every browser will warn, and federation with Entra will not work (Microsoft requires a trusted, internet-reachable HTTPS endpoint). Plan to swap in one of the above before OpenIAM as IdP for Microsoft Entra ID
Place the certificate files
sudo cp your_openiam_host.crt ca_bundle.crt /etc/pki/tls/certs/
sudo cp your_openiam_host.key /etc/pki/tls/private/Switch Apache to the SSL config
The reverse proxy installed in the previous page uses /etc/httpd/conf.d/mod_openiam.conf (HTTP). An SSL variant ships with the mod_openiam package:
cd /etc/httpd/conf.d
sudo mv mod_openiam.conf mod_openiam.conf_not_used
sudo cp /usr/share/doc/mod_openiam/conf.d/mod_openiam_ssl.conf .Edit mod_openiam_ssl.conf and point the three directives at your files:
SSLCertificateFile /etc/pki/tls/certs/your_openiam_host.crt
SSLCertificateKeyFile /etc/pki/tls/private/your_openiam_host.key
SSLCACertificateFile /etc/pki/tls/certs/ca_bundle.crtRestart and verify
sudo systemctl restart httpd
curl -I https://<openiam-host>/idp/loginPorts 80 and 443 were already opened in firewalld by the proxy installer; if you manage the firewall elsewhere, open them there too.
If it failed
httpd won't start
Key/cert mismatch or wrong paths — journalctl -u httpd shows the offending directive
Browser warns about the chain
SSLCACertificateFile missing the intermediate bundle
200 on HTTP but nothing on 443
Old mod_openiam.conf still present alongside the SSL one — only one should be active
You know this worked when…
Last updated
Was this helpful?