Search Results

By default, the Liferay platform always uses its own authentication system that checks and validates the user password in its own database. Even if you enable LDAP settings and set it as required, the Liferay platform will always check and validate the user password in its own database...

This article is a legacy article. It applies to previous versions of the Liferay product. While the article is no longer maintained, the information may still be applicable. Wiki Permissions can be "layered" because of the multiple permission levels that can go into accessing Wiki...

This article outlines a practical suggestion for avoiding issues when using multiple languages in a site along with the Liferay platform’s staging feature. Following this suggestion will help prevent future staging publication failures.  Resolution When utilizing multiple languages...

By default, Liferay encrypts the passwords that go into the database. The default algorithm is SHA-1 in 6.0 and 6.1 versions, which changed to PBKDF2WithHmacSHA1/160/128000 in version 6.2. The encryption algorithm can be changed and even turned off via the portal-ext.properties. Because...

This article outlines a practical suggestion for keeping data in sync between the staging and live site for portlets that allow changes in both places. Following the workaround will help prevent staging publication errors and failure. Resolution Generally, if staging is enabled for a...

This article describes how numeric screennames can be used in Liferay Portal. Resolution Set the following property to true in the portal-ext.properties file that will override the default functionality of being unable to create numeric screennames. # Set this to true when you want the...

The principles below are adopted from general industry standard patch management best practices. Following these will help mitigate the risk of change on production servers. Awareness Liferay communicates the availability of maintenance updates for Liferay products through Announcements....

In Liferay Portal, after completing a large LDAP import, performance may suffer because Lucene is set to re-index after every change. For example, if there are 15,000 users, Lucene will perform an index after each user is added, which will result in 15,000 index commits. This slows down...