This feature introduces the ability to map SCIM (System for Cross-domain Identity Management) attributes to Liferay custom fields. It allows organizations to synchronize additional user information from external identity systems beyond standard fields. By enabling flexible attribute mapping, Liferay supports richer identity data integration, simplifies user provisioning, and strengthens alignment with enterprise identity management standards.

Key Benefits:

• Streamlined Identity Synchronization: Automatically align user attributes between Liferay and external identity providers.

• Greater Flexibility: Support custom business requirements through configurable mappings of SCIM attributes.

• Enhanced Data Accuracy: Maintain consistent and up-to-date user information across all connected systems.

This feature enables Liferay to function as both a SAML Identity Provider (IdP) and a Service Provider (SP) at the same time. With this capability, organizations can simplify complex authentication flows—such as acting as an IdP for connected systems while also consuming authentication from an external IdP. This flexibility supports diverse deployment scenarios, multi-tenant setups, and hybrid identity architectures. user provisioning, and strengthens alignment with enterprise identity management standards.

Key Benefits:

• Increased Flexibility: Support advanced identity configurations by allowing Liferay to serve dual roles in SAML-based authentication.

• Simplified Integration: Reduce complexity in hybrid or multi-system environments by centralizing identity management within Liferay.

• Enhanced Interoperability: Enable seamless authentication across multiple systems without compromising security or compliance.

The new OIDC authentication enhancement uses the OIDC “sub” (subject) claim to identify users instead of relying on email addresses. Since the “sub” claim is a unique and permanent identifier assigned by the identity provider, it ensures consistent and reliable user recognition even if a user’s email changes or multiple providers share the same address. This improves account stability, reduces login mismatches, and enhances overall security and user experience.

Key Benefits:

• Reliable user identification: Ensures consistent recognition of users even if their email address changes.

• Eliminates account mismatches: Prevents conflicts caused by identical email addresses across different identity providers.

• Improved security: Uses the permanent and unique OIDC “sub” claim, reducing the risk of identity errors.

• Better user experience: Provides seamless authentication and minimizes login or access issues.

We created an API for allowing the user to access the OIDC accessToken from the DB by enabling the serviceLocator

The FF changes from Released to GA

The FF changes from Released to GA

The FF changes from Released to GA

Configuring Content Security Policy Headers - Liferay Official Documentation

A new, streamlined experience for managing your SSL certificates in Liferay Cloud. New status messages and alerts provide more transparency and control over your certificate lifecycle, helping you to proactively manage your domains and avoid costly downtime.

With the new Enhanced Certificate Management Experience, you'll be alerted if a certificate is misconfigured, has expired, or has been successfully renewed. Giving you a better understanding if any immediate action is required. We've also added a new "Renewal Status" column to the SSL Certificates tab, giving you at-a-glance visibility into the health of your certificates. This will empower you to identify and troubleshoot issues on your own, reducing the need for support tickets and giving you more control over your environment.

Key Benefits:

• Better visibility on certificate status.

• Better understanding of actions required in a specific certificate.

• Improved troubleshooting experience for certificate renewal errors.

Asset performance tracking in Analytics Cloud has been expanded to include interactions within Page Fragments. Previously, only assets displayed via Native Widgets (Portlets) were instrumented for performance metrics.

The previous OIDC authentication flow identified users based on their email address, which could led to mismatches if users changed their email or if different identity providers shared the same address. To ensure reliable user identification, the system now matches users using the OIDC sub (subject) claim, which is a permanent and unique identifier for each user.

Key Benefits:

• Improved identity reliability: Using the OIDC sub claim ensures each user is consistently and uniquely identified, even if their email address changes over time.

• Reduced authentication conflicts: Eliminates mismatches caused by shared or reused email addresses across different identity providers, improving security and user experience.

This mechanism is server-to-server, making it more reliable than front-channel methods that depend on the user's browser. The IdP will directly notify each RP (Relying Party aka Service Provider) that a user's session has ended by sending a signed logout_token. The RP must validate this token and terminate the corresponding local session.

Key Benefits:

• Higher reliability and security: Server-to-server logout does not rely on the user’s browser, reducing failures caused by network issues, blocked scripts, or closed sessions.

• Consistent session termination: Signed logout_token notifications ensure each RP can securely validate and promptly terminate the correct local user session.

RFC 7591 enables OAuth 2.0 clients to register dynamically with the portal’s Authorization Server, removing the need for manual client setup. It defines how Liferay can securely accept client metadata, endpoints, and credentials on-the-fly. This allows Liferay apps, modules, or external services to integrate seamlessly and scale efficiently. By automating client onboarding, it strengthens Liferay’s identity and access management capabilities.

Key Benefits:

• Eliminates manual configuration by allowing apps and external services to self-register securely with the Authorization Server.

• Speeds up integrations and scaling by automating client onboarding while improving IAM consistency and security.

RFC 8414 provides the manual and error-prone process of configuring clients to talk to authorization servers by standardizing the way for the Authorization Server to publish its configuration automatically. The specific URLs (endpoints) and capabilities can be managed through the UI.

Key Benefits:

• Eliminates the need to hardcode specific URLs, preventing configuration errors and allowing the server endpoints changes to be adapted instantly.

• Provides a standard location for clients to find the server's public keys, enabling the server to rotate security keys automatically without breaking your application or requiring a software update.

The feature is now fully released.

This features is now fully released.

This feature is now fully released. 

This features is now fully released.

Object definition creators can now set default values for specific field types during the object design phase. When a user (or an external system via API) creates a new object entry, these fields will be pre-populated with the specified values if no other data is provided.

Key Benefits:

• Reduced Manual Labor: Users no longer have to manually fill in "standard" information for every new entry.

• Data Integrity: Ensures that critical fields (like "Status" or "Initial Score") are never left empty or inconsistent during the initial creation phase.