-- PedroRio - 02 Mar 2011

XEO Application - Web.xml

The web.xml configuration file in a XEO application has some XEO-specific configurations which can be changed. The two most interesting options are located in the filter named LoginFilter. In the LoginFilter filter you have several init-param configurations, explained bellow:

LoginPage configuration

XEO has a default login page whenever someone tries to access a viewer without being authenticated. That login page is configured with the LoginPage item, which, by default has a value of Login.xvw. If you want to have a custom login page (with your own background images and logo) you put the name of that viewer as the value for this parameter. A Login viewer tipically is created by copying the default Login.xvw viewer and customized to fit your needs.

<init-param>
            <param-name>LoginPage</param-name>
            <param-value>MyCustomLogin.xvw</param-value>
</init-param>

_

MainPage configuration

The name of the viewer to which the user will be redirected (by default) from the login page. XEO has a default Main.xvw viewer but usually in your application you build your own Main viewer which you can make the default Main viewer for the application (this information can be overriden by using profiles, and associating each profiles with a Main viewer)

<init-param>
            <param-name>LoginPage</param-name>
            <param-value>Login.xvw</param-value>
</init-param>

_

ShowUserProfiles configuration

Whether or not the list of profiles should be displayed when the user makes the first attempt to login, in the Login viewer.

<init-param>
            <param-name>ShowUserProfiles</param-name>
            <param-value>true</param-value>
</init-param>

ViewerSecurityMode configuration

There are two options, for this configuration: LESS_RESTRICTED and MORE_RESTRICTED.

The MORE_RESTRICTED options (as the name implies) is a more conservative option which forces a given user to have (direct) permission to read/write/execute/etc to be able to do that action, while the LESS_RESTRICTED option will allow a given user to perform those operations if it belongs to a group that has those permissions (even if himself does not have).

In other words, with the MORE_RESTRICTED option, even if the user belongs to a group that has permission to execute a certain action, if he himself does not have that permission, he will not be able to execute that action, while the LESS_RESTRICTED option will allow him to perform that action if he is part of a group that has that permission.

<init-param>
            <param-name>ViewerSecurityMode</param-name>
            <param-value>MORE_RESTRICTED</param-value> <!--  LESS_RESTRICTED / MORE_RESTRICTED  -->
</init-param>

XWC Servlet Configuration

XEO's Servlet can be configured with two parameters, the DefaultLanguage and the LoginPageWhenExpired

The default language parameter is configured as follows (as a parameter of the XWC Servlet) - This parameter is a fallback in case the other attempts to detect the language fail

<init-param>
    <param-name>DefaultLanguage</param-name>
    <param-value>en</param-value>
</init-param>

The LoginPageWhenExpired parameter (used to declare the page where the user is redirected when a session has expired, default value is "Login.xvw")

<init-param>
   <param-name>LoginPageWhenExpired</param-name>
   <param-value>Login.xvw</param-value>
</init-param>

_


This topic: WebXEO > WebITDS > XeoPrimer > XeoPrimerWebXml
Topic revision: r5 - 2012-01-16 - PedroRio
 
This site is powered by the TWiki collaboration platform Powered by Perl

No permission to view TWiki.WebBottomBar