Search Results

All Results 6967
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Managing Expired and Future Scheduled Web Content
legacy
This article documents how the Web Content Display portlet is designed to display different versions of the same Web Content article. In particular, this article discusses the intended...
LSV-391: Security Advisory for Vulnerability With Pingback in Blogs
legacy How To
This advisory comes in response to the recent public announcement of a potential Server-Side Request Forgery (SSRF) vulnerability in Liferay Portal 7.0.4. The report talks about a perceived vulnerability for the...
Making Liferay CAPTCHA Easier to Read in Liferay Portal 6.1
legacy How To
This article is intended for legacy versions of Liferay Portal CAPTCHA is an industry standard security measure that requires users to enter what they see a small window as part of the validation process when creating an...
ThreadLocal Leaking Caused by Usages of Netty in Elasticsearch
legacy
This article documents a possible known issue where there is ThreadLocal leak shown in the console logs when shutting down the application server:...
Hiding Portlets From Guests Who Do Not Have Permission to View It
legacy How To
When view permissions for guests are unchecked for a portlet, a guest will see the following message in the portlet: You do not have the roles required to access this portlet. While...
Extension Environment Migration Tips
legacy
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....
Group mapping required for LDAP export
legacy Troubleshooting
This article addresses one issue for Active Directory users attempting to log in to the Liferay platform. Liferay is configured for use with an LDAP server (without mapping the "Group"...
Known Issue: Error With URLs Leading With Period (.) in Tomcat 8.5
legacy Troubleshooting
Customers using Tomcat 8.5 and configuring the Liferay platform with URLs that have a leading period (.) may encounter the following error: java.lang.IllegalArgumentException: An invalid domain [.example.com] was specified...