Author: Marek Posolda
At this moment, this feature is not provided in GateIn or EPP 5.* out of the box. In current GateIn, redirection after login works as follow:
- When user signs through click to Sign in button, he is always redirected to default page of default portal after his login ( http://localhost:8080/portal/private/classic/ )
- When user put private URL into browser, he is redirected to login screen and then after login, he is redirected to the requested page. For example:
- User put http://localhost:8080/portal/private/classic/sitemap into the browser and he is redirected to login screen.
- After login, user is redirected to the requested page http://localhost:8080/portal/private/classic/sitemap . (This redirections is based on value of initialURL parameter, which is send from login screen with parameters for username and password.)
This document is description of how to customize above behavior. We have created new HTTP filter called LoginRedirectFilter. Filter is able to detect login or logout of particular user. After this detection, filter is using LoginRedirectService, which is component that needs to be bind into eXo kernel for correct usage. Service is able to return correct URL for redirect based on groups of particular user. Filter then sends another HTTP request, which redirects user to requested page.
Application can be deployed into GateIn portal or EPP without need to change any other existing code on portal side. We can simply comment or uncomment particular HTTP filter and filter mapping in portal web.xml if we want to disable or enable this feature.
How to build and deploy the plugin
1) Download the code from [location will be added soon but fire an email if you need it quick] and build using "mvn clean install"
2) Copy target/exo.portal.redirectplugin-3.2.0-SNAPSHOT.jar to $GATEIN_HOME/server/default/deploy/gatein.ear/lib/
This JAR contains needed java classes, especially LoginRedirectFilter and LoginRedirectService.
4) Configure HTTP filter in portal web.xml . This can be done by adding Filter definition and Filter mapping into particular sections of file $GATEIN_HOME/server/default/deploy/gatein.ear/02portal.war/WEB-INF/web.xml
Assumption is that element filter is inserted after all other filter definitions:
And another assumption is that elements for filter-mapping are inserted after all other filter-mapping definitions:
5) LoginRedirectFilter uses LoginRedirectService to decide which URL to redirect for users of a particular group. This service needs to be configured in some of portal configuration files (for example in $GATEIN_HOME/server/default/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/common-configuration.xml ). Example configuration is below. We can see that each mapping parameter has 3 nested parameters:
- groupName - name of group and membership
- loginURL - URL to redirect after login of user from particular group is detected
- logoutURL - URL to redirect after logout of user from particular group is detected
Order of mapping elements is important because if more mappings are suitable for particular user, then algorithm will choose first found mapping. For example: User john is suitable in both groups manager:/organization/management/executive-board and *:/platform/administrators , so first mapping is chosen for him and he is redirected to /portal/private/classic/organization/management after his login.
There are another 2 parameters defaultLoginURL and defaultLogoutURL, which contains default URL to redirect if no suitable group mapping is found for our user.
So example of mapping is here:
<description>login URL to redirect if group mapping can't be found for particular user</description>
<description>logout URL to redirect if group mapping can't be found for particular user</description>
<description>Mappings of groups and pages where should be
all users from particular group redirected.</description>
6) So after update of mapping configuration in common-configuration.xml and filter configuration in web.xml, we can start the portal. We can try predefined users and we will see that:
- User john is member of first suitable group manager:/organization/management/executive-board . So after his login, he will be redirected to http://localhost:8080/portal/private/classic/organization/management and after logout to http://localhost:8080/portal/public/classic/sitemap .
- User root is not in manager:/organization/management/executive-board but he meets second group *:/platform/administrators. So after login, he will be redirected to http://localhost:8080/portal/private/classic/administration/registry and after logout to http://localhost:8080/portal/public/classic/ .
- User mary meets only last group *:/platform/users . So she will be redirected to pages in last mapping.