Portal customization

LemonLDAP::NG is shipped with 3 skins:

• pastel
• impact
• dark

You can change the skin in Manager: General Parameters > Portal > Customization > Skin.

A skin is composed of different files:

• .tpl: Perl HTML::Template files, for HTML content
• .css: CSS (styles)
• .js: Javascript
• images and other media files

A skin will often refer to the common skin, which is not a real skin, but shared skin objects (like scripts, images and CSS).

To customize a skin, the simplest way is to create a new skin folder:

cd portal/skins
mkdir myskin
mkdir myskin/css
mkdir myskin/images

Then create symbolic links on template files, as you might not want to rewrite all HTML code (else, do as you want).

cd myskin
ln -s ../pastel/*.tpl .

We include some template files that can be customized:

• customhead.tpl : HTML header markups (like CSS, js cinlusion)
• customheader.tpl : HTML code int the header div
• customfooter.tpm : HTML code in the footer div

To use custom files, delete links and copy them into your skin folder:

rm custom*
cp ../pastel/custom* .

Then you only have to write myskin/css/styles.css and add your media to myskin/images. Put all custom HTML code in the custom template files.

To configure your new skin in Manager, select the custom skin, and enter your skin name in the configuration field.

• Reset password: display a link to reset a password (for password based authentication backends)
• Auto complete: allow the browser to remember the password (for password based authentication backends)
• Require old password: used only in the password changing module of the menu, will check the old password before updating it
• Hide old password: used only if the password need to be reset by the user (LDAP password policy), will hide the old password input
• User attribute: which session attribute will be used to display Connected as in the menu
• New window: open menu links in new window
• Anti iframe protection: will kill parent frames to avoid some well known attacks