127 lines
5.4 KiB
HTML
127 lines
5.4 KiB
HTML
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
|
|
lang="en" dir="ltr">
|
|
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title></title>
|
|
<!-- metadata -->
|
|
<meta name="generator" content="Offline" />
|
|
<meta name="version" content="Offline 0.1" />
|
|
<!-- style sheet links -->
|
|
<link rel="stylesheet" media="all" type="text/css" href="../../../css/all.css" />
|
|
<link rel="stylesheet" media="screen" type="text/css" href="../../../css/screen.css" />
|
|
<link rel="stylesheet" media="print" type="text/css" href="../../../css/print.css" />
|
|
|
|
</head>
|
|
<body>
|
|
<div class="dokuwiki export">
|
|
|
|
|
|
<h1 class="sectionedit1" id="portal_menu">Portal menu</h1>
|
|
<div class="level1">
|
|
|
|
<p>
|
|
<p><div class="noteclassic">The menu is displayed if authentication is successful.
|
|
</div></p>
|
|
</p>
|
|
|
|
</div>
|
|
<!-- EDIT1 SECTION "Portal menu" [1-95] -->
|
|
<h2 class="sectionedit2" id="menu_modules">Menu modules</h2>
|
|
<div class="level2">
|
|
|
|
<p>
|
|
LemonLDAP::NG portal menu has 4 modules:
|
|
</p>
|
|
<ul>
|
|
<li class="level1"><div class="li"> <strong>Application list</strong>: display categories and applications allowed for the user</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Password change</strong>: form to change the password</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Login history</strong>: display user's last logins and last failed logins</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Logout</strong>: logout button</div>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>
|
|
Each module can be activated trough a rule, using user session information. These rules can be set trough Manager: <code>General Parameters</code> > <code>Portal</code> > <code>Menu</code> > <code>Modules activation</code>.
|
|
</p>
|
|
|
|
<p>
|
|
You can use <code>0</code> or <code>1</code> to disable/enable the module, or use a more complex rule. For example, to display the password change form only for user authenticated trough LDAP or <abbr title="Database Interface">DBI</abbr>:
|
|
</p>
|
|
<pre class="code perl"><span class="re0">$_auth</span> <span class="kw1">eq</span> LDAP <span class="kw1">or</span> <span class="re0">$_auth</span> <span class="kw1">eq</span> DBI</pre>
|
|
|
|
</div>
|
|
<!-- EDIT2 SECTION "Menu modules" [96-827] -->
|
|
<h2 class="sectionedit3" id="categories_and_applications">Categories and applications</h2>
|
|
<div class="level2">
|
|
|
|
<p>
|
|
<a href="../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">Configuring the virtual hosts</a> is not sufficient to display an application in the menu. Indeed, a virtual host can contain several applications (<a href="http://vhost.example.com/appli1" class="urlextern" title="http://vhost.example.com/appli1" rel="nofollow">http://vhost.example.com/appli1</a>, <a href="http://vhost.example.com/appli2" class="urlextern" title="http://vhost.example.com/appli2" rel="nofollow">http://vhost.example.com/appli2</a>).
|
|
</p>
|
|
|
|
<p>
|
|
In Manager, you can configure categories and applications in <code>General Parameters</code> > <code>Portal</code> > <code>Menu</code> > <code>Categories and applications</code>.
|
|
</p>
|
|
|
|
<p>
|
|
Category parameters:
|
|
</p>
|
|
<ul>
|
|
<li class="level1"><div class="li"> <strong>Key</strong>: category identifier</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Name</strong>: display text</div>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>
|
|
Application parameters:
|
|
</p>
|
|
|
|
<p>
|
|
<a href="/_detail/documentation/manager-menu-application.png?id=documentation%3A1.9%3Aportalmenu" class="media" title="documentation:manager-menu-application.png"><img src="../../../media/documentation/manager-menu-application.png" class="mediacenter" alt="" /></a>
|
|
</p>
|
|
<ul>
|
|
<li class="level1"><div class="li"> <strong>Key</strong>: application identifier</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Name</strong>: display text</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Address</strong>: <abbr title="Uniform Resource Locator">URL</abbr> of application</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Description</strong></div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Logo</strong>: file name to use as logo</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>Display</strong>:</div>
|
|
<ul>
|
|
<li class="level2"><div class="li"> <strong>auto</strong>: display only if the user can access it</div>
|
|
</li>
|
|
<li class="level2"><div class="li"> <strong>on</strong>: always display</div>
|
|
</li>
|
|
<li class="level2"><div class="li"> <strong>off</strong>: never display</div>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>
|
|
<p><div class="notetip">Category and application key can have a digit as first character, which will allow to display categories in the right order (categories and applications are displayed in alphabetical order).
|
|
</div></p>
|
|
</p>
|
|
|
|
<p>
|
|
<a href="/_detail/documentation/manager-menu-application-logo.png?id=documentation%3A1.9%3Aportalmenu" class="media" title="documentation:manager-menu-application-logo.png"><img src="../../../media/documentation/manager-menu-application-logo.png" class="mediacenter" alt="" /></a>
|
|
</p>
|
|
|
|
<p>
|
|
<p><div class="notetip">The chosen logo file must be in portal applications logos directory (<code>portal/skins/common/apps/</code>). You can set a custom logo by choosing <code>My logo</code>, set the logo file name, and copy the logo file in portal applications logos directory
|
|
</div></p>
|
|
</p>
|
|
|
|
</div>
|
|
</div><!-- closes <div class="dokuwiki export">--> |