System Settings

< enportal | 5.6 | admin | system administration


The system is installed with pre-defined settings for both login page and look and feel (LAF) and without a password policy in place. Through the Advanced Tab -> System Settings, administrators can assign a system login page and system LAF that will override the default out of the box settings as well as creating a system password policy.

System Settings sub-menu


Page Contents

1. System Login Page

The system login page is the page that all users will see when they first access the system.

Login pages must exist on the enPortal server in the [INSTALL_HOME]/server/webapps/enportal/login_pages directory. Take a look in this directory to see the available options included with a default enPortal install:

  • (no sub-directory): classic Edge Dark login page
  • edgeLight: classic Edge Light login page
  • edgeDark_css3: new Dark login page themed using CSS for easier customization
  • edgeLight_css3: new Light login page themed using CSS for easier customization
  • edgeFlat: new Flat login page themed using CSS for easier customization
  • edgeMarketing: example promotional login page
The login page can be changed for individual domains, by specifying a custom login page per domain. The login page specified for a domain takes precedence over the system setting.


1.1. Assigning a System Login Page

System Login Page administration page.

Perform the following steps to assign a system login page:

  1. Mouse over the Advanced tab and then System Settings and click on System Login Page.
  2. From the table click within the Location column to preview a login page
  3. To change the current selection use the Select column.
  4. Click the Save button.
  5. Logout of the portal and confirm that the correct login page is displayed.

1.2. Modifying Login Pages

Do not directly modify the login pages shipped with enPortal as these files are not backed up and may be replaced on upgrade.

Modifying the login page may be as minimal as changing the logo, or adjusting some of the theming, or completely writing everything custom. In all cases the existing shipped pages and resources should serve as a starting template. The recommended approach is to:

  1. Choose one of the existing login pages to start with, it's best to use the CSS-based pages if the goal is to simply change the logo and look'n'feel.
  2. Make a copy of the login page sub-directory with all it's files and sub-directories into a new directory, for example: [INSTALL_HOME]/server/webapps/enportal/login_pages/customLoginPage
  3. Make changes only to this new copy as needed.
  4. Update the system to use the new login page (see previous section)
  5. Except for the system shipped login pages, all other sub-directories under login_pages are automatically included in backup archives.

To test make sure to log out of enPortal, clear your browser cache, and reload the login page.

1.2.1. Custom Login Page Examples

For more information and examples on modifying or creating completely custom login pages refer to the Custom Login Pages documentation.

2. Look and Feel


You can specify a default system look and feel (LAF) so that the appropriate LAF is displayed when a user logs in. A default LAF can also be assigned to a role, domain, or user.

2.1. Order of Precedence


The order of precedence for LAF assignments is as follows:

This means that when an user logs in, the system determines if an LAF has been assigned to the role, then it displays the the LAF assigned to the role. If there is no LAF assigned to the role, then it displays the LAF assigned to the user, and if there is no assignment, it checks the domain and then the system.


2.2. Assigning a System Look and Feel


Perform the following steps to assign a system look and feel (LAF).

  1. Log in to enPortal as an administrator. (Non-administrative users are not allowed to set the System LAF.)
  2. Mouse over the Advanced tab and then System Settings and click on System LAF.
  3. Select the desired LAF from the drop-down box.
  4. Click the Save button.
  5. Refresh the browser page and confirm that the correct LAF is displayed assuming no LAF is assigned to administrator user, role, or domain directly.

2.3. Navigation Breadcrumb Support

With deployments that have many tab menus with sub-menus and content provisioned it can be useful for end-users to see the current selected channel and it's hierarchy in the form of breadcrumbs. The default enPortal look and feel supports this feature however it is disabled by default. To enable:

  1. Edit or create [INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/custom.properties
  2. Add the following on a separate line and save the file:
    provisioning.showBreadCrumb=true
  3. restart enPortal.
Example with breadcrumbs enabled.

3. System Password Policy


3.1. System Password Policy


The setting in the system password policy will affect all users in the portal system and in external LDAP. When setting the policy for LDAP users, it is strongly recommended that the system policy matches that of LDAP because most of the LDAPs do not give good error messages when user's password failed its policy.

The password policy can be changed for individual domains, by specifying a custom password policy per domain. The password policy specified for a domain takes precedence over the system setting.


3.2. Assigning a System Password Policy


Perform the following steps to assign a system password policy.

  1. Log in to enPortal as an administrator.
  2. Mouse over the Advanced tab and then System Settings and click on System Password Policy.
  3. Make the desired changes in the three sections: Password, Syntax, and Lockout
  4. Click the Save button.
  5. Confirm that the correct policy is applied by changing a test user's password.

3.3. LDAP Authentication

When using external authentication via LDAP the password policy should mirror the policy defined for the LDAP system. It may be more applicable to apply this policy just to the LDAP Domain.

Refer to the LDAP Configuration documentation for more information on configuring LDAP including supported features depending on the LDAP server.