Authentication Service
The portal Authentication Service contains the configuration properties for portal authentication. Authentication means that users identify themselves in order to gain access to the system. Usually they do this by a user ID and password.
In the WebSphere® Integrated Solutions Console, the portal Authentication Service is listed as WP AuthenticationService.
- authentication.execute.portal.jaas.login = (false)
- Use this property to enable or disable the execution of the portal
JAAS login:
- false
- Disables the execution of the portal JAAS login. This is the default. Disable this property only if you have no JAAS Login Modules defined for the portal application login configuration.
- true
- Enables the execution of the portal JAAS login. You can enable this property if you have JAAS Login Modules defined for the portal application login configuration.
- authentication.isLoginUrlActive = (true)
- Use this property to enable or disable the automatic login URL
in Portal. Notes:
- This property was introduced with APAR PI13472 and CF12. To be able to use this property, you must have CF12 installed.
- This is a java.lang.Boolean property.
- true
- Enables the automatic login URL. This is the default.
- false
- Disables the automatic login URL
Use the following properties to define the custom
filters in the various authentication filter chains in the portal.
Each of these properties takes a comma-separated list of the fully
qualified class names of the custom filter implementations. For concept
information about authentication filters see the topic about Configuring
authentication filters.
- login.explicit.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered for an explicit login by user name and password. The classes listed in this property must implement the interface com.ibm.portal.auth.ExplicitLoginFilter.
- login.implicit.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered for an implicit login, that is if the user is already authenticated to WebSphere Application Server but has no portal session yet. The classes listed in this property must implement the interface com.ibm.portal.auth.ImplicitLoginFilter.
- logout.explicit.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered for an explicit logout. The classes listed in this property must implement the interface com.ibm.portal.auth.ExplicitLogoutFilter.
- logout.implicit.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered for an implicit logout, that is if the user got a session timeout. The classes listed in this property must implement the interface com.ibm.portal.auth.ImplicitLogoutFilter.
- sessiontimeout.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered directly after an idle timeout of the session occurred. The classes listed in this property must implement the interface com.ibm.portal.auth.SessionTimeoutFilter.
- sessionvalidation.filterchain = <none>
- Use this property to specify the custom filters for the filter chain that is triggered for every request before the action handling and rendering is processed. The classes listed in this property must implement the interface com.ibm.portal.auth.SessionValidationFilter.
- jsessionid.cookie.expire = (true)
- Use this property to determine whether the portal impersonation
logout invalidates the HTTP session, but does not expire the session
cookie. That cookie is typically the JSESSIONID cookie. Specify one
of the following values:
- true
- If you specify this value, the session cookie expires in the web browser. This value is the default value.
- false
- If you specify this value, the session cookie does not expire in the web browser. As a result, the impersonation process can remain on a single server when it changes between user IDs.
- filterchain.properties = <none>
- Use an arbitrary set of properties according to the previous pattern to specify properties for any of your custom filters. The property value is then available to the specified filter class in the SecurityFilterConfig object passed to its init method.