Databases Reference
In-Depth Information
Liferay Portal configuration best practices
In this section, we will learn the various Liferay Portal configuration settings for
achieving best performance. These configuration settings are categorized into
multiple sections. Let's learn these configuration settings in detail.
Servlet filter configuration
Liferay Portal ships with a bunch of features which are implemented using servlet
filters. An example of such feature includes NTLM SSO integration, CAS SSO
integration, SharePoint integration, and so on. Irrespective of whether we are using
such features, all requests pass through a chain of filters depending upon the filter
configuration. So, a fraction of CPU and memory will be consumed by some of the
unnecessary filters for every request. Liferay Portal provides a way to disable these
features. In this section, we will learn about these filters in detail. We will also learn
how to disable them to improve performance.
The auto login filter
Liferay Portal implements the auto login feature using the auto login filter. The
auto login feature is used to sign in to the Portal automatically without using the
traditional sign-in mechanism. For example, if we want to sign in to Liferay Portal
by passing the username and password in URL requests, we will need to bypass the
traditional sign-in form. This feature intercepts every secure request using the HTTP
servlet filter. The auto login functionality is implemented using the hook-based
mechanism to allow customizations. The auto login filter delegates every request
to a chain of auto login hooks. If any of the auto login hooks return a success result,
it automatically signs the user in. By default, the auto login filter is used for the
following features:
• CAS SSO integration
• Facebook SSO integration
• NTLM SSO integration
• OpenID SSO integration
• OpenSSO integration
• Site Minder SSO integration
• The Remember Me feature (saves login information using the Remember Me
checkbox in the Sign in portlet)
