Allow users to move display pages containing Object or Form widgets across environments
Key benefit:
Addresses a feature gap when moving content pages across environments
Release Notes
Allow users to move display pages containing Object or Form widgets across environments
Key benefit:
Addresses a feature gap when moving content pages across environments
Liferay Cloud now provides CI/CD support for Client Extensions on Liferay PaaS. Developers can integrate Client Extensions into their Git-based CI/CD pipelines, ensuring automatic builds and deployments alongside core Liferay services. This update enables automated validation, independent deployments, and faster release cycles for Client Extensions.
Highlights:
Dedicated CI/CD Pipeline: Separate build pipeline for Client Extensions to prevent conflicts with core Liferay services.
Automated Builds: Every commit triggers a new Client Extensions build, packaged as a LUFFA archive.
Independent Deployments: Client Extensions builds deploy separately, improving release flexibility.
Seamless Integration: Works with existing Git-based workflows on Liferay PaaS.
Zero Downtime Deployments: Deploy client extensions without affecting the main Liferay service.
The SSL Certificate Management view now provides expiration alerts for certificates nearing expiration (e.g., within 30 days) and those that have already expired. Certificates must now be defined exclusively through the LCP.json
file, simplifying management and ensuring consistency across deployments. This update reduces manual errors and ensures secure and uninterrupted deployments.
Highlights:
Expiration Alerts: Notifications for certificates nearing expiration and those already expired, with clear visual indicators.
Exclusive LCP.json Configuration: Certificates can only be defined through the LCP.json
file.
Improved Visibility: Organized list view showing certificate names, types, associated domains, and expiration dates.
Proactive Management: Tools and alerts to help users maintain secure SSL/TLS configurations.
The vendor has deprecated OpenSSO/OpenAM, so there's no reason for us to keep it. The alternative, which is PingAM can be integrated using our existing OpenID connector or SAML Authentication.