Move documentation from 2.0 to 1.9
This commit is contained in:
Clément Oudot
parent
4a1f957fdd
commit
1b3063f271
File diff suppressed because one or more lines are too long
|
|
@ -34,7 +34,7 @@ To use Active Directory as LDAP backend, you must change few things in the manag
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> Use “Active Directory” as authentication, userDB and passwordDBbackends,</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Export sAMAccountName in a variable declared in <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables</a></div>
|
||||
<li class="level1"><div class="li"> Export sAMAccountName in a variable declared in <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Change the user attribute to store in Apache logs <em>(“General Parameters » Logs » REMOTE_USER”)</em>: use the variable declared above</div>
|
||||
</li>
|
||||
|
|
@ -47,7 +47,7 @@ To use Active Directory as LDAP backend, you must change few things in the manag
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> Choose “Apache” as authentication module <em>(“General Parameters » Authentication modules » Authentication module”)</em></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/authapache.html" class="wikilink1" title="documentation:2.0:authapache">Configure the Apache server</a> that host the portal to use the Apache Kerberos authentication module</div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/authapache.html" class="wikilink1" title="documentation:1.9:authapache">Configure the Apache server</a> that host the portal to use the Apache Kerberos authentication module</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -32,13 +32,8 @@
|
|||
Applications listed bellow are known to be easy to integrate in <abbr title="LemonLDAP::NG">LL::NG</abbr>. As <abbr title="LemonLDAP::NG">LL::NG</abbr> works like classic WebSSO (like Siteminder™), many other applications are easy to integrate.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="noteclassic">Find other documentation on <a href="https://wikit.firewall-services.com/doku.php?id=lemonldap_ng" class="urlextern" title="https://wikit.firewall-services.com/doku.php?id=lemonldap_ng" rel="nofollow">Firewall Services site</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT2 SECTION "Known supported applications" [29-380] -->
|
||||
<!-- EDIT2 SECTION "Known supported applications" [29-249] -->
|
||||
<h3 class="sectionedit3" id="mail_agenda_groupware">Mail, Agenda, Groupware</h3>
|
||||
<div class="level3">
|
||||
<div class="table sectionedit4"><table class="inline">
|
||||
|
|
@ -48,12 +43,12 @@ Applications listed bellow are known to be easy to integrate in <abbr title="Lem
|
|||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/obm.html" class="media" title="documentation:2.0:applications:obm"><img src="../../../media/applications/obm_logo.png" class="media" alt="" /></a> </td><td class="col1 leftalign"> <a href="../../documentation/2.0/applications/sympa.html" class="media" title="documentation:2.0:applications:sympa"><img src="../../../media/applications/sympa_logo.png" class="media" alt="" /></a> </td><td class="col2 rightalign"> <a href="../../documentation/2.0/applications/zimbra.html" class="media" title="documentation:2.0:applications:zimbra"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col3 rightalign"> <a href="../../documentation/2.0/applications/roundcube.html" class="media" title="documentation:2.0:applications:roundcube"><img src="../../../media/applications/roundcube_logo.png" class="media" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/obm.html" class="media" title="documentation:1.9:applications:obm"><img src="../../../media/applications/obm_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/sympa.html" class="media" title="documentation:1.9:applications:sympa"><img src="../../../media/applications/sympa_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="../../documentation/1.9/applications/zimbra.html" class="media" title="documentation:1.9:applications:zimbra"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col3 centeralign"> <a href="../../documentation/1.9/applications/roundcube.html" class="media" title="documentation:1.9:applications:roundcube"><img src="../../../media/applications/roundcube_logo.png" class="media" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT4 TABLE [416-709] -->
|
||||
<!-- EDIT4 TABLE [285-581] -->
|
||||
</div>
|
||||
<!-- EDIT3 SECTION "Mail, Agenda, Groupware" [381-710] -->
|
||||
<!-- EDIT3 SECTION "Mail, Agenda, Groupware" [250-582] -->
|
||||
<h3 class="sectionedit5" id="wiki">Wiki</h3>
|
||||
<div class="level3">
|
||||
<div class="table sectionedit6"><table class="inline">
|
||||
|
|
@ -63,63 +58,63 @@ Applications listed bellow are known to be easy to integrate in <abbr title="Lem
|
|||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 leftalign"> <a href="../../documentation/2.0/applications/dokuwiki.html" class="media" title="documentation:2.0:applications:dokuwiki"><img src="../../../media/applications/dokuwiki_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/2.0/applications/mediawiki.html" class="media" title="documentation:2.0:applications:mediawiki"><img src="../../../media/applications/mediawiki_logo.png" class="media" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/dokuwiki.html" class="media" title="documentation:1.9:applications:dokuwiki"><img src="../../../media/applications/dokuwiki_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/mediawiki.html" class="media" title="documentation:1.9:applications:mediawiki"><img src="../../../media/applications/mediawiki_logo.png" class="media" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT6 TABLE [727-892] -->
|
||||
<!-- EDIT6 TABLE [599-765] -->
|
||||
</div>
|
||||
<!-- EDIT5 SECTION "Wiki" [711-893] -->
|
||||
<h3 class="sectionedit7" id="cms_portal">CMS, Portal</h3>
|
||||
<!-- EDIT5 SECTION "Wiki" [583-766] -->
|
||||
<h3 class="sectionedit7" id="cms_portal_ecm">CMS, Portal, ECM</h3>
|
||||
<div class="level3">
|
||||
<div class="table sectionedit8"><table class="inline">
|
||||
<thead>
|
||||
<tr class="row0 roweven">
|
||||
<th class="col0 centeralign"> Drupal </th><th class="col1 centeralign"> Liferay </th>
|
||||
<th class="col0 centeralign"> Drupal </th><th class="col1 centeralign"> Liferay </th><th class="col2 centeralign"> Alfresco </th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/drupal.html" class="media" title="documentation:2.0:applications:drupal"><img src="../../../media/applications/drupal_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/2.0/applications/liferay.html" class="media" title="documentation:2.0:applications:liferay"><img src="../../../media/applications/liferay_logo.png" class="media" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/drupal.html" class="media" title="documentation:1.9:applications:drupal"><img src="../../../media/applications/drupal_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/liferay.html" class="media" title="documentation:1.9:applications:liferay"><img src="../../../media/applications/liferay_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="../../documentation/1.9/applications/alfresco.html" class="media" title="documentation:1.9:applications:alfresco"><img src="../../../media/applications/alfresco_logo.png" class="media" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT8 TABLE [917-1072] -->
|
||||
<!-- EDIT8 TABLE [795-1030] -->
|
||||
</div>
|
||||
<!-- EDIT7 SECTION "CMS, Portal" [894-1073] -->
|
||||
<!-- EDIT7 SECTION "CMS, Portal, ECM" [767-1031] -->
|
||||
<h3 class="sectionedit9" id="bugtracker_service_management">Bugtracker, Service Management</h3>
|
||||
<div class="level3">
|
||||
<div class="table sectionedit10"><table class="inline">
|
||||
<thead>
|
||||
<tr class="row0 roweven">
|
||||
<th class="col0 centeralign"> Bugzilla </th><th class="col1 leftalign"> GLPI </th>
|
||||
<th class="col0 centeralign"> Bugzilla </th><th class="col1 centeralign"> GLPI </th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/bugzilla.html" class="media" title="documentation:2.0:applications:bugzilla"><img src="../../../media/applications/bugzilla_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="https://forge.indepnet.net/projects/glpi/wiki/GLPI-SSO" class="media" title="https://forge.indepnet.net/projects/glpi/wiki/GLPI-SSO" rel="nofollow"><img src="../../../media/applications/glpi_logo.png" class="media" alt="" width="100" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/bugzilla.html" class="media" title="documentation:1.9:applications:bugzilla"><img src="../../../media/applications/bugzilla_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="https://forge.indepnet.net/projects/glpi/wiki/GLPI-SSO" class="media" title="https://forge.indepnet.net/projects/glpi/wiki/GLPI-SSO" rel="nofollow"><img src="../../../media/applications/glpi_logo.png" class="media" alt="" width="100" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT10 TABLE [1116-1306] -->
|
||||
<!-- EDIT10 TABLE [1074-1265] -->
|
||||
</div>
|
||||
<!-- EDIT9 SECTION "Bugtracker, Service Management" [1074-1307] -->
|
||||
<!-- EDIT9 SECTION "Bugtracker, Service Management" [1032-1266] -->
|
||||
<h3 class="sectionedit11" id="other">Other</h3>
|
||||
<div class="level3">
|
||||
<div class="table sectionedit12"><table class="inline">
|
||||
<thead>
|
||||
<tr class="row0 roweven">
|
||||
<th class="col0 centeralign"> GRR </th><th class="col1 leftalign"> phpLDAPadmin </th><th class="col2 centeralign"> LinShare </th><th class="col3 centeralign"> SAP </th>
|
||||
<th class="col0 centeralign"> GRR </th><th class="col1 centeralign"> phpLDAPadmin </th><th class="col2 centeralign"> LinShare </th><th class="col3 centeralign"> SAP </th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="http://grr.mutualibre.org/documentation/body.php?id=35" class="media" title="http://grr.mutualibre.org/documentation/body.php?id=35" rel="nofollow"><img src="../../../media/applications/grr_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/2.0/applications/phpldapadmin.html" class="media" title="documentation:2.0:applications:phpldapadmin"><img src="../../../media/applications/phpldapadmin_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://www.linpki.org/projects/linshare/wiki/HttpHeaderSSOEN" class="media" title="http://www.linpki.org/projects/linshare/wiki/HttpHeaderSSOEN" rel="nofollow"><img src="../../../media/applications/linshare_logo.png" class="media" alt="" /></a> </td><td class="col3 centeralign"> <a href="http://help.sap.com/saphelp_nw70/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.htm" class="media" title="http://help.sap.com/saphelp_nw70/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="http://grr.mutualibre.org/documentation/body.php?id=35" class="media" title="http://grr.mutualibre.org/documentation/body.php?id=35" rel="nofollow"><img src="../../../media/applications/grr_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/phpldapadmin.html" class="media" title="documentation:1.9:applications:phpldapadmin"><img src="../../../media/applications/phpldapadmin_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://www.linpki.org/projects/linshare/wiki/HttpHeaderSSOEN" class="media" title="http://www.linpki.org/projects/linshare/wiki/HttpHeaderSSOEN" rel="nofollow"><img src="../../../media/applications/linshare_logo.png" class="media" alt="" /></a> </td><td class="col3 centeralign"> <a href="http://help.sap.com/saphelp_nw70/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.htm" class="media" title="http://help.sap.com/saphelp_nw70/helpdata/en/d0/a3d940c2653126e10000000a1550b0/frameset.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td>
|
||||
</tr>
|
||||
<tr class="row2 roweven">
|
||||
<th class="col0 centeralign"> LimeSurvey </th><th class="col1 leftalign"> </th><th class="col2 leftalign"> </th><th class="col3 leftalign"> </th>
|
||||
</tr>
|
||||
<tr class="row3 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/limesurvey.html" class="media" title="documentation:2.0:applications:limesurvey"><img src="../../../media/applications/limesurvey_logo.png" class="media" title="LimeSurvey" alt="LimeSurvey" width="120" /></a> </td><td class="col1"> </td><td class="col2"> </td><td class="col3"> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/limesurvey.html" class="media" title="documentation:1.9:applications:limesurvey"><img src="../../../media/applications/limesurvey_logo.png" class="media" title="LimeSurvey" alt="LimeSurvey" width="120" /></a> </td><td class="col1"> </td><td class="col2"> </td><td class="col3"> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT12 TABLE [1325-1902] -->
|
||||
<!-- EDIT12 TABLE [1284-1862] -->
|
||||
</div>
|
||||
<!-- EDIT11 SECTION "Other" [1308-1903] -->
|
||||
<!-- EDIT11 SECTION "Other" [1267-1863] -->
|
||||
<h2 class="sectionedit13" id="frameworks">Frameworks</h2>
|
||||
<div class="level2">
|
||||
<div class="table sectionedit14"><table class="inline">
|
||||
|
|
@ -129,12 +124,12 @@ Applications listed bellow are known to be easy to integrate in <abbr title="Lem
|
|||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/spring.html" class="media" title="documentation:2.0:applications:spring"><img src="../../../media/applications/spring_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/2.0/applications/django.html" class="media" title="documentation:2.0:applications:django"><img src="../../../media/applications/django_logo.png" class="media" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/spring.html" class="media" title="documentation:1.9:applications:spring"><img src="../../../media/applications/spring_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/django.html" class="media" title="documentation:1.9:applications:django"><img src="../../../media/applications/django_logo.png" class="media" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT14 TABLE [1928-2095] -->
|
||||
<!-- EDIT14 TABLE [1888-2055] -->
|
||||
</div>
|
||||
<!-- EDIT13 SECTION "Frameworks" [1904-2096] -->
|
||||
<!-- EDIT13 SECTION "Frameworks" [1864-2056] -->
|
||||
<h2 class="sectionedit15" id="connectors">Connectors</h2>
|
||||
<div class="level2">
|
||||
<div class="table sectionedit16"><table class="inline">
|
||||
|
|
@ -144,37 +139,37 @@ Applications listed bellow are known to be easy to integrate in <abbr title="Lem
|
|||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/authbasic.html" class="media" title="documentation:2.0:applications:authbasic"><img src="../../../media/applications/http_logo.png" class="media" alt="" /></a> </td><td class="col1 rightalign"> <a href="../../documentation/2.0/applications/tomcat.html" class="media" title="documentation:2.0:applications:tomcat"><img src="../../../media/applications/tomcat_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="../../documentation/2.0/applications/nginx.html" class="media" title="documentation:2.0:applications:nginx"><img src="../../../media/applications/nginx_logo.png" class="media" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/authbasic.html" class="media" title="documentation:1.9:applications:authbasic"><img src="../../../media/applications/http_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.9/applications/tomcat.html" class="media" title="documentation:1.9:applications:tomcat"><img src="../../../media/applications/tomcat_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="../../documentation/1.9/applications/nginx.html" class="media" title="documentation:1.9:applications:nginx"><img src="../../../media/applications/nginx_logo.png" class="media" alt="" /></a> </td>
|
||||
</tr>
|
||||
<tr class="row2 roweven">
|
||||
<th class="col0 centeralign" colspan="3"> Some applications using it </th>
|
||||
</tr>
|
||||
<tr class="row3 rowodd">
|
||||
<td class="col0"> <a href="http://en.wikipedia.org/wiki/Outlook_Web_App" class="urlextern" title="http://en.wikipedia.org/wiki/Outlook_Web_App" rel="nofollow">Outlook Web App</a> <br/>
|
||||
<a href="http://en.wikipedia.org/wiki/IBM_Lotus_iNotes" class="urlextern" title="http://en.wikipedia.org/wiki/IBM_Lotus_iNotes" rel="nofollow">IBM Lotus iNotes</a> </td><td class="col1 leftalign"> <a href="http://www.lambdaprobe.org" class="urlextern" title="http://www.lambdaprobe.org" rel="nofollow">Probe</a> <br/>
|
||||
<td class="col0 centeralign"> <a href="http://en.wikipedia.org/wiki/Outlook_Web_App" class="urlextern" title="http://en.wikipedia.org/wiki/Outlook_Web_App" rel="nofollow">Outlook Web App</a> <br/>
|
||||
<a href="http://en.wikipedia.org/wiki/IBM_Lotus_iNotes" class="urlextern" title="http://en.wikipedia.org/wiki/IBM_Lotus_iNotes" rel="nofollow">IBM Lotus iNotes</a> </td><td class="col1 centeralign"> <a href="http://www.lambdaprobe.org" class="urlextern" title="http://www.lambdaprobe.org" rel="nofollow">Probe</a> <br/>
|
||||
<a href="http://fr.lutece.paris.fr" class="urlextern" title="http://fr.lutece.paris.fr" rel="nofollow">Lutece</a> </td><td class="col2"> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT16 TABLE [2121-2608] -->
|
||||
<!-- EDIT16 TABLE [2081-2572] -->
|
||||
</div>
|
||||
<!-- EDIT15 SECTION "Connectors" [2097-2609] -->
|
||||
<!-- EDIT15 SECTION "Connectors" [2057-2573] -->
|
||||
<h2 class="sectionedit17" id="saml_connectors">SAML connectors</h2>
|
||||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<p><div class="noteclassic">This requires to configure <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>.
|
||||
<p><div class="noteclassic">This requires to configure <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
<div class="table sectionedit18"><table class="inline">
|
||||
<thead>
|
||||
<tr class="row0 roweven">
|
||||
<th class="col0 centeralign"> Google Apps </th><th class="col1 centeralign"> Zimbra </th><th class="col2 centeralign"> SAP </th><th class="col3 centeralign"> Cornerstone </th><th class="col4"> SalesForce </th>
|
||||
<th class="col0 centeralign"> Google Apps </th><th class="col1 centeralign"> Zimbra </th><th class="col2 centeralign"> SAP </th><th class="col3 centeralign"> Cornerstone </th><th class="col4 centeralign"> SalesForce </th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/googleapps.html" class="media" title="documentation:2.0:applications:googleapps"><img src="../../../media/applications/googleapps_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="media" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" class="media" title="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td><td class="col3 rightalign"> <a href="../../documentation/2.0/applications/cornerstone.html" class="media" title="documentation:2.0:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 leftalign"> <a href="../../documentation/2.0/applications/salesforce.html" class="media" title="documentation:2.0:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/googleapps.html" class="media" title="documentation:1.9:applications:googleapps"><img src="../../../media/applications/googleapps_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="media" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" class="media" title="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td><td class="col3 centeralign"> <a href="../../documentation/1.9/applications/cornerstone.html" class="media" title="documentation:1.9:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 centeralign"> <a href="../../documentation/1.9/applications/salesforce.html" class="media" title="documentation:1.9:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT18 TABLE [2729-3270] -->
|
||||
<!-- EDIT18 TABLE [2693-3238] -->
|
||||
</div>
|
||||
</div><!-- closes <div class="dokuwiki export">-->
|
||||
158
doc/pages/documentation/1.9/applications/alfresco.html
Normal file
158
doc/pages/documentation/1.9/applications/alfresco.html
Normal file
|
|
@ -0,0 +1,158 @@
|
|||
|
||||
<!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="alfresco">Alfresco</h1>
|
||||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<img src="../../../../media/applications/alfresco_logo.png" class="mediacenter" alt="" />
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT1 SECTION "Alfresco" [1-71] -->
|
||||
<h2 class="sectionedit2" id="presentation">Presentation</h2>
|
||||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<a href="https://www.alfresco.com/" class="urlextern" title="https://www.alfresco.com/" rel="nofollow">Alfresco</a> is an ECM/BPM software.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Since 4.0 release, it offers an easy way to configure <abbr title="Single Sign On">SSO</abbr> thanks to authentication subsystems.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you use an older version, you need to refer to the following documentation: <a href="https://wiki.alfresco.com/wiki/SSO" class="urlextern" title="https://wiki.alfresco.com/wiki/SSO" rel="nofollow">https://wiki.alfresco.com/wiki/SSO</a>
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT2 SECTION "Presentation" [72-395] -->
|
||||
<h2 class="sectionedit3" id="configuration">Configuration</h2>
|
||||
<div class="level2">
|
||||
|
||||
</div>
|
||||
<!-- EDIT3 SECTION "Configuration" [396-422] -->
|
||||
<h3 class="sectionedit4" id="alfresco1">Alfresco</h3>
|
||||
<div class="level3">
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">The official documentation can be found here: <a href="http://docs.alfresco.com/4.0/tasks/auth-alfrescoexternal-sso.html" class="urlextern" title="http://docs.alfresco.com/4.0/tasks/auth-alfrescoexternal-sso.html" rel="nofollow">http://docs.alfresco.com/4.0/tasks/auth-alfrescoexternal-sso.html</a>
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
You need to find the following files in your Alfresco installation:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <code>alfresco-global.properties</code> (ex: <code>tomcat/shared/classes/alfresco-global.properties</code>)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <code>share-config-custom.xml</code> (ex: <code>tomcat/shared/classes/alfresco/web-extension/share-config-custom.xml</code>)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
The first will allow to configure <abbr title="Single Sign On">SSO</abbr> for the alfresco webapp, and the other for the share webapp.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Edit first <code>alfresco-global.properties</code> and add the following:
|
||||
</p>
|
||||
<pre class="code file java">### SSO ###
|
||||
authentication.<span class="me1">chain</span><span class="sy0">=</span>external1<span class="sy0">:</span>external
|
||||
external.<span class="me1">authentication</span>.<span class="me1">enabled</span><span class="sy0">=</span><span class="kw2">true</span>
|
||||
external.<span class="me1">authentication</span>.<span class="me1">defaultAdministratorUserNames</span><span class="sy0">=</span>
|
||||
external.<span class="me1">authentication</span>.<span class="me1">proxyUserName</span><span class="sy0">=</span>
|
||||
external.<span class="me1">authentication</span>.<span class="me1">proxyHeader</span><span class="sy0">=</span>Auth<span class="sy0">-</span>User
|
||||
external.<span class="me1">authentication</span>.<span class="me1">userIdPattern</span><span class="sy0">=</span></pre>
|
||||
|
||||
<p>
|
||||
Edit then <code>share-config-custom.xml</code> and uncomment the last part. In the <code><endpoint></code>, change <code><connector-id></code> value to <code>alfrescoHeader</code> and change the <code><userHeader></code> value to <code>Auth-User</code>:
|
||||
</p>
|
||||
<pre class="code file xml"> <span class="sc3"><span class="re1"><config</span> <span class="re0">evaluator</span>=<span class="st0">"string-compare"</span> <span class="re0">condition</span>=<span class="st0">"Remote"</span><span class="re2">></span></span>
|
||||
<span class="sc3"><span class="re1"><remote<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><keystore<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><path<span class="re2">></span></span></span>alfresco/web-extension/alfresco-system.p12<span class="sc3"><span class="re1"></path<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><type<span class="re2">></span></span></span>pkcs12<span class="sc3"><span class="re1"></type<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><password<span class="re2">></span></span></span>alfresco-system<span class="sc3"><span class="re1"></password<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></keystore<span class="re2">></span></span></span>
|
||||
|
||||
<span class="sc3"><span class="re1"><connector<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><id<span class="re2">></span></span></span>alfrescoCookie<span class="sc3"><span class="re1"></id<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><name<span class="re2">></span></span></span>Alfresco Connector<span class="sc3"><span class="re1"></name<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><description<span class="re2">></span></span></span>Connects to an Alfresco instance using cookie-based authentication<span class="sc3"><span class="re1"></description<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><class<span class="re2">></span></span></span>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector<span class="sc3"><span class="re1"></class<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></connector<span class="re2">></span></span></span>
|
||||
|
||||
<span class="sc3"><span class="re1"><connector<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><id<span class="re2">></span></span></span>alfrescoHeader<span class="sc3"><span class="re1"></id<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><name<span class="re2">></span></span></span>Alfresco Connector<span class="sc3"><span class="re1"></name<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><description<span class="re2">></span></span></span>Connects to an Alfresco instance using header and cookie-based authentication<span class="sc3"><span class="re1"></description<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><class<span class="re2">></span></span></span>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector<span class="sc3"><span class="re1"></class<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><userHeader<span class="re2">></span></span></span>Auth-User<span class="sc3"><span class="re1"></userHeader<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></connector<span class="re2">></span></span></span>
|
||||
|
||||
<span class="sc3"><span class="re1"><endpoint<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><id<span class="re2">></span></span></span>alfresco<span class="sc3"><span class="re1"></id<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><name<span class="re2">></span></span></span>Alfresco - user access<span class="sc3"><span class="re1"></name<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><description<span class="re2">></span></span></span>Access to Alfresco Repository WebScripts that require user authentication<span class="sc3"><span class="re1"></description<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><connector-id<span class="re2">></span></span></span>alfrescoHeader<span class="sc3"><span class="re1"></connector-id<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><endpoint-url<span class="re2">></span></span></span>http://localhost:8080/alfresco/wcs<span class="sc3"><span class="re1"></endpoint-url<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><identity<span class="re2">></span></span></span>user<span class="sc3"><span class="re1"></identity<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"><external-auth<span class="re2">></span></span></span>true<span class="sc3"><span class="re1"></external-auth<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></endpoint<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></remote<span class="re2">></span></span></span>
|
||||
<span class="sc3"><span class="re1"></config<span class="re2">></span></span></span></pre>
|
||||
|
||||
<p>
|
||||
You need to restart Tomcat to apply changes.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notewarning">Now you can log in with a simple HTTP header. You need to restrict access to Alfresco to <abbr title="LemonLDAP::NG">LL::NG</abbr>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT4 SECTION "Alfresco" [423-3119] -->
|
||||
<h3 class="sectionedit5" id="llng">LL::NG</h3>
|
||||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Just set the <code>Auth-User</code> header with the attribute that carries the user login, for example <code>$uid</code>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
You can intercept the logout with this rule: <code>^/share/page/dologout ⇒ logout_app_sso</code>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT5 SECTION "LL::NG" [3120-3332] -->
|
||||
<h2 class="sectionedit6" id="other_resources">Other resources</h2>
|
||||
<div class="level2">
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="https://www.youtube.com/watch?v=5tS0XrC_-rw" class="urlextern" title="https://www.youtube.com/watch?v=5tS0XrC_-rw" rel="nofollow">DevCon 2012: Unlocking the Secrets of Alfresco Authentication, Mehdi Belmekki</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div><!-- closes <div class="dokuwiki export">-->
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/http_logo.png?id=documentation%3A2.0%3Aapplications%3Aauthbasic" class="media" title="applications:http_logo.png"><img src="../../../../media/applications/http_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/http_logo.png?id=documentation%3A1.9%3Aapplications%3Aauthbasic" class="media" title="applications:http_logo.png"><img src="../../../../media/applications/http_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -52,7 +52,7 @@ So HTTP Basic Autentication is managed trough an HTTP header (<code>Authorizatio
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> Data should not contains accents or special characters, as HTTP protocol only allow <abbr title="American Standard Code for Information Interchange">ASCII</abbr> values in header (but depending on the HTTP server, you can use ISO encoded values)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> You need to forward the password, which can be the user main password (if <a href="../../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">password is stored in session</a>, or any user attribute (if you keep secondary passwords in users database).</div>
|
||||
<li class="level1"><div class="li"> You need to forward the password, which can be the user main password (if <a href="../../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">password is stored in session</a>, or any user attribute (if you keep secondary passwords in users database).</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -66,12 +66,12 @@ The Basic Authentication relies on a specific HTTP header, as described above. S
|
|||
</p>
|
||||
|
||||
<p>
|
||||
For example, to forward login (<code>$uid</code>) and password (<code>$_password</code> if <a href="../../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">password is stored in session</a>):
|
||||
For example, to forward login (<code>$uid</code>) and password (<code>$_password</code> if <a href="../../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">password is stored in session</a>):
|
||||
</p>
|
||||
<pre class="code">Authorization => "Basic ".encode_base64("$uid:$_password")</pre>
|
||||
|
||||
<p>
|
||||
<abbr title="LemonLDAP::NG">LL::NG</abbr> provides a special function named <a href="../../../documentation/2.0/extendedfunctions.html#basic" class="wikilink1" title="documentation:2.0:extendedfunctions">basic</a> to build this header.
|
||||
<abbr title="LemonLDAP::NG">LL::NG</abbr> provides a special function named <a href="../../../documentation/1.9/extendedfunctions.html#basic" class="wikilink1" title="documentation:1.9:extendedfunctions">basic</a> to build this header.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/bugzilla_logo.png?id=documentation%3A2.0%3Aapplications%3Abugzilla" class="media" title="applications:bugzilla_logo.png"><img src="../../../../media/applications/bugzilla_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/bugzilla_logo.png?id=documentation%3A1.9%3Aapplications%3Abugzilla" class="media" title="applications:bugzilla_logo.png"><img src="../../../../media/applications/bugzilla_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -82,7 +82,7 @@ Then set:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure Bugzilla virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure Bugzilla virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> bugzilla.example.com
|
||||
|
|
@ -99,15 +99,15 @@ Configure Bugzilla virtual host like other <a href="../../../documentation/2.0/c
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Bugzilla.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Bugzilla.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Configure the following <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a>.
|
||||
Configure the following <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">headers</a>.
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Auth-User</strong>: $uid</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/csod_logo.png?id=documentation%3A2.0%3Aapplications%3Acornerstone" class="media" title="applications:csod_logo.png"><img src="../../../../media/applications/csod_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/csod_logo.png?id=documentation%3A1.9%3Aapplications%3Acornerstone" class="media" title="applications:csod_logo.png"><img src="../../../../media/applications/csod_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -42,7 +42,7 @@ To work with <abbr title="LemonLDAP::NG">LL::NG</abbr> it requires:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> An enterprise account</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></div>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Registered users on CSOD with the same email than those used by <abbr title="LemonLDAP::NG">LL::NG</abbr> (email will be the NameID exchanged between CSOD and <abbr title="LemonLDAP::NG">LL::NG</abbr>)</div>
|
||||
</li>
|
||||
|
|
@ -59,7 +59,7 @@ To work with <abbr title="LemonLDAP::NG">LL::NG</abbr> it requires:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>,
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a>,
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -117,7 +117,7 @@ For the certificate, you can build it from the signing private key registered in
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-export-priv-key.png?id=documentation%3A2.0%3Aapplications%3Acornerstone" class="media" title="documentation:googleapps-export-priv-key.png"><img src="../../../../media/documentation/googleapps-export-priv-key.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-export-priv-key.png?id=documentation%3A1.9%3Aapplications%3Acornerstone" class="media" title="documentation:googleapps-export-priv-key.png"><img src="../../../../media/documentation/googleapps-export-priv-key.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/dokuwiki_logo.png?id=documentation%3A2.0%3Aapplications%3Adokuwiki" class="media" title="applications:dokuwiki_logo.png"><img src="../../../../media/applications/dokuwiki_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/dokuwiki_logo.png?id=documentation%3A1.9%3Aapplications%3Adokuwiki" class="media" title="applications:dokuwiki_logo.png"><img src="../../../../media/applications/dokuwiki_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -77,7 +77,7 @@ Edit Dokuwiki local configuration (<code>conf/local.php</code>) and set <code>le
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure Dokuwiki virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure Dokuwiki virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> dokuwiki.example.com
|
||||
|
|
@ -89,7 +89,7 @@ Configure Dokuwiki virtual host like other <a href="../../../documentation/2.0/c
|
|||
</<span class="kw3">VirtualHost</span>></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you are protecting Dokuwiki with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/2.0/header_remote_user_conversion.html" class="wikilink1" title="documentation:2.0:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
<p><div class="noteimportant">If you are protecting Dokuwiki with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/1.9/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.9:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -99,15 +99,15 @@ Configure Dokuwiki virtual host like other <a href="../../../documentation/2.0/c
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Dokuwiki.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Dokuwiki.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/drupal_logo.png?id=documentation%3A2.0%3Aapplications%3Adrupal" class="media" title="applications:drupal_logo.png"><img src="../../../../media/applications/drupal_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/drupal_logo.png?id=documentation%3A1.9%3Aapplications%3Adrupal" class="media" title="applications:drupal_logo.png"><img src="../../../../media/applications/drupal_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -65,7 +65,7 @@ Go on Drupal administration interface and enable the Webserver Auth module.
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure Drupal virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure Drupal virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> drupal.example.com
|
||||
|
|
@ -77,7 +77,7 @@ Configure Drupal virtual host like other <a href="../../../documentation/2.0/con
|
|||
</<span class="kw3">VirtualHost</span>></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you are protecting Drupal with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/2.0/header_remote_user_conversion.html" class="wikilink1" title="documentation:2.0:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
<p><div class="noteimportant">If you are protecting Drupal with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/1.9/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.9:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -87,15 +87,15 @@ Configure Drupal virtual host like other <a href="../../../documentation/2.0/con
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Drupal.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Drupal.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/googleapps_logo.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="applications:googleapps_logo.png"><img src="../../../../media/applications/googleapps_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/googleapps_logo.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="applications:googleapps_logo.png"><img src="../../../../media/applications/googleapps_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -42,7 +42,7 @@ To work with <abbr title="LemonLDAP::NG">LL::NG</abbr> it requires:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> An <a href="http://www.google.com/apps/intl/en/business/index.html" class="urlextern" title="http://www.google.com/apps/intl/en/business/index.html" rel="nofollow">enterprise Google Apps account</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></div>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Registered users on Google Apps with the same email than those used by <abbr title="LemonLDAP::NG">LL::NG</abbr> (email will be the NameID exchanged between Google Apps and <abbr title="LemonLDAP::NG">LL::NG</abbr>)</div>
|
||||
</li>
|
||||
|
|
@ -68,7 +68,7 @@ As administrator, go in Google Apps control panel and click on Advanced tools:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-menu.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-menu.png"><img src="../../../../media/documentation/googleapps-menu.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-menu.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-menu.png"><img src="../../../../media/documentation/googleapps-menu.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -76,7 +76,7 @@ Then select <code>Set up single sign-on (<abbr title="Single Sign On">SSO</abbr>
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-sso.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-sso.png"><img src="../../../../media/documentation/googleapps-sso.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-sso.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-sso.png"><img src="../../../../media/documentation/googleapps-sso.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -84,7 +84,7 @@ Now configure all <abbr title="Security Assertion Markup Language">SAML</abbr> p
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-ssoconfig.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-ssoconfig.png"><img src="../../../../media/documentation/googleapps-ssoconfig.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-ssoconfig.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-ssoconfig.png"><img src="../../../../media/documentation/googleapps-ssoconfig.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Enable Single Sign-On</strong>: check the box. Uncheck it to disable <abbr title="Security Assertion Markup Language">SAML</abbr> authentication (for example, if your Identity Provider is down).</div>
|
||||
|
|
@ -107,7 +107,7 @@ For the certificate, you can build it from the signing private key registered in
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-export-priv-key.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-export-priv-key.png"><img src="../../../../media/documentation/googleapps-export-priv-key.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-export-priv-key.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-export-priv-key.png"><img src="../../../../media/documentation/googleapps-export-priv-key.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -130,7 +130,7 @@ You can now the upload the certificate (<code>cert.pem</code>) on Google Apps.
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>,
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a>,
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -166,11 +166,11 @@ Now we will add Google Apps as a new <abbr title="Security Assertion Markup Lang
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
You can add a link in <a href="../../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">application menu</a> to display Google Apps to users.
|
||||
You can add a link in <a href="../../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">application menu</a> to display Google Apps to users.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/googleapps-manager-application.png?id=documentation%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-manager-application.png"><img src="../../../../media/documentation/googleapps-manager-application.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/googleapps-manager-application.png?id=documentation%3A1.9%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-manager-application.png"><img src="../../../../media/documentation/googleapps-manager-application.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -198,11 +198,11 @@ Google Apps does not support Single Logout (SLO).
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Google Apps has a configuration parameter to redirect user on a specific <abbr title="Uniform Resource Locator">URL</abbr> after Google Apps logout (see <a href="#google_apps_control_panel" title="documentation:2.0:applications:googleapps ↵" class="wikilink1">Google Apps control panel</a>).
|
||||
Google Apps has a configuration parameter to redirect user on a specific <abbr title="Uniform Resource Locator">URL</abbr> after Google Apps logout (see <a href="#google_apps_control_panel" title="documentation:1.9:applications:googleapps ↵" class="wikilink1">Google Apps control panel</a>).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
To manage the other way (<abbr title="LemonLDAP::NG">LL::NG</abbr> → Google Apps), you can add a dedicated <a href="../../../documentation/2.0/logoutforward.html" class="wikilink1" title="documentation:2.0:logoutforward">logout forward rule</a>:
|
||||
To manage the other way (<abbr title="LemonLDAP::NG">LL::NG</abbr> → Google Apps), you can add a dedicated <a href="../../../documentation/1.9/logoutforward.html" class="wikilink1" title="documentation:1.9:logoutforward">logout forward rule</a>:
|
||||
</p>
|
||||
<pre class="code">GoogleApps => http://www.google.com/calendar/hosted/mydomain.org/logout</pre>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/liferay_logo.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="applications:liferay_logo.png"><img src="../../../../media/applications/liferay_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/liferay_logo.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="applications:liferay_logo.png"><img src="../../../../media/applications/liferay_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -74,7 +74,7 @@ Access to Liferay (first time):
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_1.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_1.png"><img src="../../../../media/documentation/liferay_1.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_1.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_1.png"><img src="../../../../media/documentation/liferay_1.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -82,7 +82,7 @@ Login as administrator:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_2.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_2.png"><img src="../../../../media/documentation/liferay_2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_2.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_2.png"><img src="../../../../media/documentation/liferay_2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -90,7 +90,7 @@ Go to <code>My Account</code>:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_3.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_3.png"><img src="../../../../media/documentation/liferay_3.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_3.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_3.png"><img src="../../../../media/documentation/liferay_3.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -98,7 +98,7 @@ Go to <code>Portal</code> » <code>Settings</code>:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_4.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_4.png"><img src="../../../../media/documentation/liferay_4.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_4.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_4.png"><img src="../../../../media/documentation/liferay_4.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -106,7 +106,7 @@ Go to <code>Configuration</code> » <code>Authentication</code>:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_5.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_5.png"><img src="../../../../media/documentation/liferay_5.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_5.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_5.png"><img src="../../../../media/documentation/liferay_5.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -123,7 +123,7 @@ In <code>General</code>, fill at least the following information:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_6.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_6.png"><img src="../../../../media/documentation/liferay_6.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_6.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_6.png"><img src="../../../../media/documentation/liferay_6.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -143,14 +143,14 @@ Then use the <code>SiteMinder</code> tab to configure <abbr title="Single Sign O
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Enabled</strong>: Yes</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Import from LDAP</strong>: Yes (see <a href="#presentation" title="documentation:2.0:applications:liferay ↵" class="wikilink1">presentation</a>)</div>
|
||||
<li class="level1"><div class="li"> <strong>Import from LDAP</strong>: Yes (see <a href="#presentation" title="documentation:1.9:applications:liferay ↵" class="wikilink1">presentation</a>)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>User Header</strong>: Auth-User (case sensitive)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/liferay_7.png?id=documentation%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_7.png"><img src="../../../../media/documentation/liferay_7.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/documentation/liferay_7.png?id=documentation%3A1.9%3Aapplications%3Aliferay" class="media" title="documentation:liferay_7.png"><img src="../../../../media/documentation/liferay_7.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -164,7 +164,7 @@ Then use the <code>SiteMinder</code> tab to configure <abbr title="Single Sign O
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure Liferay virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure Liferay virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> liferay.example.com
|
||||
|
|
@ -181,16 +181,16 @@ Configure Liferay virtual host like other <a href="../../../documentation/2.0/co
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Liferay.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Liferay.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>. You can add a rule for logout:
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>. You can add a rule for logout:
|
||||
</p>
|
||||
<pre class="code"> ^/c/portal/logout => logout_sso</pre>
|
||||
|
||||
<p>
|
||||
Configure the <code>Auth-User</code> <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">header</a>.
|
||||
Configure the <code>Auth-User</code> <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">header</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/limesurvey_logo.png?id=documentation%3A2.0%3Aapplications%3Alimesurvey" class="media" title="applications:limesurvey_logo.png"><img src="../../../../media/applications/limesurvey_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/limesurvey_logo.png?id=documentation%3A1.9%3Aapplications%3Alimesurvey" class="media" title="applications:limesurvey_logo.png"><img src="../../../../media/applications/limesurvey_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -99,7 +99,7 @@ The configuration is done in config.php:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure LimeSurvey virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure LimeSurvey virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> limesurvey.example.com
|
||||
|
|
@ -124,7 +124,7 @@ Configure LimeSurvey virtual host like other <a href="../../../documentation/2.0
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for LimeSurvey.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for LimeSurvey.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -155,7 +155,7 @@ Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemon
|
|||
</table></div>
|
||||
<!-- EDIT7 TABLE [2400-2618] -->
|
||||
<p>
|
||||
<p><div class="notetip">You can manage roles with the <a href="../../../documentation/2.0/rbac.html" class="wikilink1" title="documentation:2.0:rbac">RBAC model</a> or by using groups.
|
||||
<p><div class="notetip">You can manage roles with the <a href="../../../documentation/1.9/rbac.html" class="wikilink1" title="documentation:1.9:rbac">RBAC model</a> or by using groups.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/mediawiki_logo.png?id=documentation%3A2.0%3Aapplications%3Amediawiki" class="media" title="applications:mediawiki_logo.png"><img src="../../../../media/applications/mediawiki_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/mediawiki_logo.png?id=documentation%3A1.9%3Aapplications%3Amediawiki" class="media" title="applications:mediawiki_logo.png"><img src="../../../../media/applications/mediawiki_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -103,7 +103,7 @@ Then edit MediaWiki local settings
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure MediaWiki virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure MediaWiki virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> mediawiki.example.com
|
||||
|
|
@ -115,7 +115,7 @@ Configure MediaWiki virtual host like other <a href="../../../documentation/2.0/
|
|||
</<span class="kw3">VirtualHost</span>></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you are protecting MediaWiki with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/2.0/header_remote_user_conversion.html" class="wikilink1" title="documentation:2.0:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
<p><div class="noteimportant">If you are protecting MediaWiki with <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, <a href="../../../documentation/1.9/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.9:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -125,16 +125,16 @@ Configure MediaWiki virtual host like other <a href="../../../documentation/2.0/
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for MediaWiki.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for MediaWiki.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>. You can also add a rule for logout:
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>. You can also add a rule for logout:
|
||||
</p>
|
||||
<pre class="code">Userlogout => logout_sso</pre>
|
||||
|
||||
<p>
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
If using <abbr title="LemonLDAP::NG">LL::NG</abbr> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">header</a>, else no headers are needed.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/obm_logo.png?id=documentation%3A2.0%3Aapplications%3Aobm" class="media" title="applications:obm_logo.png"><img src="../../../../media/applications/obm_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/obm_logo.png?id=documentation%3A1.9%3Aapplications%3Aobm" class="media" title="applications:obm_logo.png"><img src="../../../../media/applications/obm_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -168,7 +168,7 @@ Edit also OBM Apache configuration to enable <abbr title="LemonLDAP::NG">LL::NG<
|
|||
</<span class="kw3">VirtualHost</span>></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">OBM Apache configuration must be loaded <strong>after</strong> <abbr title="LemonLDAP::NG">LL::NG</abbr> <a href="../../../documentation/2.0/configlocation.html#apache" class="wikilink1" title="documentation:2.0:configlocation">Apache configuration</a>.
|
||||
<p><div class="noteimportant">OBM Apache configuration must be loaded <strong>after</strong> <abbr title="LemonLDAP::NG">LL::NG</abbr> <a href="../../../documentation/1.9/configlocation.html#apache" class="wikilink1" title="documentation:1.9:configlocation">Apache configuration</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -203,7 +203,7 @@ To add these attributes, go in Manager, <code>Variables</code> » <code>Exported
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you plan to forward user's password to OBM, then you have to <a href="../../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">keep the password in session</a>.
|
||||
<p><div class="noteimportant">If you plan to forward user's password to OBM, then you have to <a href="../../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">keep the password in session</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -316,7 +316,7 @@ Define headers used in OBM mapping, for example:
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Do not forget to add OBM in <a href="../../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">applications menu</a>.
|
||||
Do not forget to add OBM in <a href="../../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">applications menu</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/phpldapadmin_logo.png?id=documentation%3A2.0%3Aapplications%3Aphpldapadmin" class="media" title="applications:phpldapadmin_logo.png"><img src="../../../../media/applications/phpldapadmin_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/phpldapadmin_logo.png?id=documentation%3A1.9%3Aapplications%3Aphpldapadmin" class="media" title="applications:phpldapadmin_logo.png"><img src="../../../../media/applications/phpldapadmin_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -68,7 +68,7 @@ Just set the authentication type to <code>config</code> and indicate <abbr title
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure phpLDAPadmin virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
|
||||
Configure phpLDAPadmin virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> phpldapadmin.example.com
|
||||
|
|
@ -85,15 +85,15 @@ Configure phpLDAPadmin virtual host like other <a href="../../../documentation/2
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for phpLDAPadmin.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for phpLDAPadmin.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
No <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a> are required.
|
||||
No <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">headers</a> are required.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -54,7 +54,7 @@
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<p><div class="noteclassic">To be able to forward password to RoundCube, see <a href="../../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">how to store password in session</a>
|
||||
<p><div class="noteclassic">To be able to forward password to RoundCube, see <a href="../../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">how to store password in session</a>
|
||||
</div></p>
|
||||
</p>
|
||||
<ul>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/salesforce-logo.jpg?id=documentation%3A2.0%3Aapplications%3Asalesforce" class="media" title="applications:salesforce-logo.jpg"><img src="../../../../media/applications/salesforce-logo.jpg" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/salesforce-logo.jpg?id=documentation%3A1.9%3Aapplications%3Asalesforce" class="media" title="applications:salesforce-logo.jpg"><img src="../../../../media/applications/salesforce-logo.jpg" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -33,7 +33,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<span class="curid"><a href="../../../documentation/2.0/applications/salesforce.html" class="wikilink1" title="documentation:2.0:applications:salesforce">Salesforce</a></span> Salesforce Inc. is a cloud computing company. It is best known for their CRM products and social networking applications.
|
||||
<span class="curid"><a href="../../../documentation/1.9/applications/salesforce.html" class="wikilink1" title="documentation:1.9:applications:salesforce">Salesforce</a></span> Salesforce Inc. is a cloud computing company. It is best known for their CRM products and social networking applications.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -48,7 +48,7 @@ This page presents the SP initiated mode.
|
|||
To work with <abbr title="LemonLDAP::NG">LL::NG</abbr> it requires:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></div>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> configured as <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ To work with <abbr title="LemonLDAP::NG">LL::NG</abbr> it requires:
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as a <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>.
|
||||
You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as a <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -67,7 +67,7 @@ You should have configured <abbr title="LemonLDAP::NG">LL::NG</abbr> as a <a hre
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/my_domain_salesforce-resize-web.png?id=documentation%3A2.0%3Aapplications%3Asalesforce" class="media" title="applications:my_domain_salesforce-resize-web.png"><img src="../../../../media/applications/my_domain_salesforce-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/my_domain_salesforce-resize-web.png?id=documentation%3A1.9%3Aapplications%3Asalesforce" class="media" title="applications:my_domain_salesforce-resize-web.png"><img src="../../../../media/applications/my_domain_salesforce-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -111,7 +111,7 @@ Salesforce is not able to read metadata, you must fill the information into a fo
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/saml_sso_settings-resize-web.png?id=documentation%3A2.0%3Aapplications%3Asalesforce" class="media" title="applications:saml_sso_settings-resize-web.png"><img src="../../../../media/applications/saml_sso_settings-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/saml_sso_settings-resize-web.png?id=documentation%3A1.9%3Aapplications%3Asalesforce" class="media" title="applications:saml_sso_settings-resize-web.png"><img src="../../../../media/applications/saml_sso_settings-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -164,7 +164,7 @@ Finally, configure for each user his Federation ID value. It will be the link be
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/user_federation_id-resize-web.png?id=documentation%3A2.0%3Aapplications%3Asalesforce" class="media" title="applications:user_federation_id-resize-web.png"><img src="../../../../media/applications/user_federation_id-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/user_federation_id-resize-web.png?id=documentation%3A1.9%3Aapplications%3Asalesforce" class="media" title="applications:user_federation_id-resize-web.png"><img src="../../../../media/applications/user_federation_id-resize-web.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -172,7 +172,7 @@ Once this is completed, click to export the Salesforce metadata and import them
|
|||
</p>
|
||||
|
||||
<p>
|
||||
See <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">Register partner Service Provider on LemonLDAP::NG</a> configuration chapter.
|
||||
See <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">Register partner Service Provider on LemonLDAP::NG</a> configuration chapter.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/spring_logo.png?id=documentation%3A2.0%3Aapplications%3Aspring" class="media" title="applications:spring_logo.png"><img src="../../../../media/applications/spring_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/spring_logo.png?id=documentation%3A1.9%3Aapplications%3Aspring" class="media" title="applications:spring_logo.png"><img src="../../../../media/applications/spring_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/sympa_logo.png?id=documentation%3A2.0%3Aapplications%3Asympa" class="media" title="applications:sympa_logo.png"><img src="../../../../media/applications/sympa_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/sympa_logo.png?id=documentation%3A1.9%3Aapplications%3Asympa" class="media" title="applications:sympa_logo.png"><img src="../../../../media/applications/sympa_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -82,7 +82,7 @@ Choose one of the following method:
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Configure Sympa virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a> but use Sympa Handler instead of default Handler.
|
||||
Configure Sympa virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a> but use Sympa Handler instead of default Handler.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> sympa.example.com
|
||||
|
|
@ -101,11 +101,11 @@ Configure Sympa virtual host like other <a href="../../../documentation/2.0/conf
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Sympa.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Sympa.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -170,7 +170,7 @@ You can also use <portal>?logout=1 as logout_url to remove LemonLDAP::NG s
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Configure Sympa virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a> but protect only magic authentication <abbr title="Uniform Resource Locator">URL</abbr>.
|
||||
Configure Sympa virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a> but protect only magic authentication <abbr title="Uniform Resource Locator">URL</abbr>.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> sympa.example.com
|
||||
|
|
@ -194,11 +194,11 @@ Configure Sympa virtual host like other <a href="../../../documentation/2.0/conf
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Sympa.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Sympa.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a> and define the following <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a>:
|
||||
Configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a> and define the following <a href="../../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">headers</a>:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Auth-User</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/tomcat_logo.png?id=documentation%3A2.0%3Aapplications%3Atomcat" class="media" title="applications:tomcat_logo.png"><img src="../../../../media/applications/tomcat_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/tomcat_logo.png?id=documentation%3A1.9%3Aapplications%3Atomcat" class="media" title="applications:tomcat_logo.png"><img src="../../../../media/applications/tomcat_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -73,7 +73,7 @@ Copy <code>ValveLemonLDAPNG.jar</code> in <code><TOMCAT_HOME>/server/lib</
|
|||
<pre class="code">cp ValveLemonLDAPNG.jar server/lib/</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">If needed, you can <a href="#compilation" title="documentation:2.0:applications:tomcat ↵" class="wikilink1">recompile the valve from the sources</a>.
|
||||
<p><div class="notetip">If needed, you can <a href="#compilation" title="documentation:1.9:applications:tomcat ↵" class="wikilink1">recompile the valve from the sources</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="/_detail/applications/zimbra_logo.png?id=documentation%3A2.0%3Aapplications%3Azimbra" class="media" title="applications:zimbra_logo.png"><img src="../../../../media/applications/zimbra_logo.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/applications/zimbra_logo.png?id=documentation%3A1.9%3Aapplications%3Azimbra" class="media" title="applications:zimbra_logo.png"><img src="../../../../media/applications/zimbra_logo.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -41,7 +41,7 @@ Zimbra use a specific <a href="http://wiki.zimbra.com/index.php?title=Preauth" c
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">Zimbra can also be connected to <abbr title="LemonLDAP::NG">LL::NG</abbr> via <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML protocol</a> (see <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="urlextern" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow">Zimbra blog</a>).
|
||||
<p><div class="notetip">Zimbra can also be connected to <abbr title="LemonLDAP::NG">LL::NG</abbr> via <a href="../../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML protocol</a> (see <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="urlextern" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow">Zimbra blog</a>).
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -83,7 +83,7 @@ See <a href="http://wiki.zimbra.com/index.php?title=Preauth#Preparing_a_domain_f
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Choose for example <a href="http://zimbra.example.com/zimbrasso" class="urlextern" title="http://zimbra.example.com/zimbrasso" rel="nofollow">http://zimbra.example.com/zimbrasso</a> as <abbr title="Single Sign On">SSO</abbr> <abbr title="Uniform Resource Locator">URL</abbr> and <a href="../../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">set it in application menu</a>.
|
||||
Choose for example <a href="http://zimbra.example.com/zimbrasso" class="urlextern" title="http://zimbra.example.com/zimbrasso" rel="nofollow">http://zimbra.example.com/zimbrasso</a> as <abbr title="Single Sign On">SSO</abbr> <abbr title="Uniform Resource Locator">URL</abbr> and <a href="../../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">set it in application menu</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -92,7 +92,7 @@ Choose for example <a href="http://zimbra.example.com/zimbrasso" class="urlexter
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
You will configure Zimbra virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a> but you will use Zimbra Handler instead of default Handler.
|
||||
You will configure Zimbra virtual host like other <a href="../../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a> but you will use Zimbra Handler instead of default Handler.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *>
|
||||
<span class="kw1">ServerName</span> zimbra.example.com
|
||||
|
|
@ -110,11 +110,11 @@ You will configure Zimbra virtual host like other <a href="../../../documentatio
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Go to the Manager and <a href="../../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">create a new virtual host</a> for Zimbra.
|
||||
Go to the Manager and <a href="../../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">create a new virtual host</a> for Zimbra.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
|
||||
Just configure the <a href="../../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">access rules</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -39,7 +39,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
The Active Directory module is based on the <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP module</a>, with these features:
|
||||
The Active Directory module is based on the <a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP module</a>, with these features:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Specific default values for filters to match AD schema</div>
|
||||
|
|
@ -56,7 +56,7 @@ The Active Directory module is based on the <a href="../../documentation/2.0/aut
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
The configuration is the same as the <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP module</a>.
|
||||
The configuration is the same as the <a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP module</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -62,7 +62,7 @@ In General Parameters > Authentication modules, choose <code>Apache</code> as
|
|||
</p>
|
||||
|
||||
<p>
|
||||
You may want to failback to another authentication backend in case of the Apache authentication fails. Use then the <a href="../../documentation/2.0/authmulti.html" class="wikilink1" title="documentation:2.0:authmulti">Multiple authentication module</a>, for example:
|
||||
You may want to failback to another authentication backend in case of the Apache authentication fails. Use then the <a href="../../documentation/1.9/authmulti.html" class="wikilink1" title="documentation:1.9:authmulti">Multiple authentication module</a>, for example:
|
||||
</p>
|
||||
<pre class="code">Multi Apache;LDAP</pre>
|
||||
|
||||
|
|
@ -101,7 +101,7 @@ The Apache configuration depends on the module you choose, you need to look at t
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
The Kerberos configuration is quite complex. You can find some configuration tips <a href="../../documentation/2.0/kerberos.html" class="wikilink1" title="documentation:2.0:kerberos">on this page</a>.
|
||||
The Kerberos configuration is quite complex. You can find some configuration tips <a href="../../documentation/1.9/kerberos.html" class="wikilink1" title="documentation:1.9:kerberos">on this page</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -56,7 +56,7 @@ In Manager, go in <code>General Parameters</code> > <code>Authentication modu
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">You can then choose any other module for users and password but if you want to totally delegate authentication to BrowserID, choose <a href="../../documentation/2.0/authnull.html" class="wikilink1" title="documentation:2.0:authnull">None</a> for users and password.
|
||||
<p><div class="notetip">You can then choose any other module for users and password but if you want to totally delegate authentication to BrowserID, choose <a href="../../documentation/1.9/authnull.html" class="wikilink1" title="documentation:1.9:authnull">None</a> for users and password.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -43,7 +43,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS server</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/1.9/idpcas.html" class="wikilink1" title="documentation:1.9:idpcas">CAS server</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -56,11 +56,11 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
They can then be forwarded to applications trough <a href="../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">HTTP headers</a>.
|
||||
They can then be forwarded to applications trough <a href="../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">HTTP headers</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip"><abbr title="Central Authentication Service">CAS</abbr> authentication will automatically add a <a href="../../documentation/2.0/logoutforward.html" class="wikilink1" title="documentation:2.0:logoutforward">logout forward rule</a> on <abbr title="Central Authentication Service">CAS</abbr> server logout <abbr title="Uniform Resource Locator">URL</abbr> in order to close <abbr title="Central Authentication Service">CAS</abbr> session on <abbr title="LemonLDAP::NG">LL::NG</abbr> logout.
|
||||
<p><div class="notetip"><abbr title="Central Authentication Service">CAS</abbr> authentication will automatically add a <a href="../../documentation/1.9/logoutforward.html" class="wikilink1" title="documentation:1.9:logoutforward">logout forward rule</a> on <abbr title="Central Authentication Service">CAS</abbr> server logout <abbr title="Uniform Resource Locator">URL</abbr> in order to close <abbr title="Central Authentication Service">CAS</abbr> session on <abbr title="LemonLDAP::NG">LL::NG</abbr> logout.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ By default, only the configured authentication backend is available for users.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Contrary to <a href="../../documentation/2.0/authmulti.html" class="wikilink1" title="documentation:2.0:authmulti">multiple backend stacking</a>, backend choice will present all available authentication methods to users, who will choose the one they want.
|
||||
Contrary to <a href="../../documentation/1.9/authmulti.html" class="wikilink1" title="documentation:1.9:authmulti">multiple backend stacking</a>, backend choice will present all available authentication methods to users, who will choose the one they want.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -103,7 +103,7 @@ Then, go in <code>Choice Parameters</code>:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-authchoice.png?id=documentation%3A2.0%3Aauthchoice" class="media" title="documentation:manager-authchoice.png"><img src="../../../media/documentation/manager-authchoice.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-authchoice.png?id=documentation%3A1.9%3Aauthchoice" class="media" title="documentation:manager-authchoice.png"><img src="../../../media/documentation/manager-authchoice.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -203,7 +203,7 @@ As <abbr title="Database Interface">DBI</abbr> is a login/password based module,
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> increased (+1) if portal is protected by SSL (HTTPS)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/2.0/portalcustom.html" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>)</div>
|
||||
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/1.9/portalcustom.html" class="wikilink1" title="documentation:1.9:portalcustom">portal customization</a>)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -218,7 +218,7 @@ As <abbr title="Database Interface">DBI</abbr> is a login/password based module,
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
List of columns to query to fill user session. See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
List of columns to query to fill user session. See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -86,7 +86,7 @@ Select Demonstration for authentication, user and password backend.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
You can also modify list of exported variables. Only uid, cn and mail attributes are available. See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
You can also modify list of exported variables. Only uid, cn and mail attributes are available. See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -82,7 +82,7 @@ If you use Facebook as user database, declare values in exported variables :
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -43,7 +43,7 @@ Google proposes to allow applications to reuse its own authentication process us
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notewarning">OpenID 2.0 support is closed since 20th April 2015. If you still need to use Google login after this date, use <a href="../../documentation/2.0/authopenidconnect.html" class="wikilink1" title="documentation:2.0:authopenidconnect">OpenID Connect authentication module</a>.
|
||||
<p><div class="notewarning">OpenID 2.0 support is closed since 20th April 2015. If you still need to use Google login after this date, use <a href="../../documentation/1.9/authopenidconnect.html" class="wikilink1" title="documentation:1.9:authopenidconnect">OpenID Connect authentication module</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ Use the name you want but this values in the value field. If you want to require
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -53,7 +53,7 @@
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
This works with every LDAP v2 or v3 server, including <a href="../../documentation/2.0/authad.html" class="wikilink1" title="documentation:2.0:authad">Active Directory</a>.
|
||||
This works with every LDAP v2 or v3 server, including <a href="../../documentation/1.9/authad.html" class="wikilink1" title="documentation:1.9:authad">Active Directory</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -79,7 +79,7 @@ In Manager, go in <code>General Parameters</code> > <code>Authentication modu
|
|||
|
||||
<p>
|
||||
<p><div class="notetip">
|
||||
For <a href="../../documentation/2.0/authad.html" class="wikilink1" title="documentation:2.0:authad">Active Directory</a>, choose <code>Active Directory</code> instead of <code>LDAP</code>.
|
||||
For <a href="../../documentation/1.9/authad.html" class="wikilink1" title="documentation:1.9:authad">Active Directory</a>, choose <code>Active Directory</code> instead of <code>LDAP</code>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ As LDAP is a login/password based module, the authentication level can be:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> increased (+1) if portal is protected by SSL (HTTPS)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/2.0/portalcustom.html" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>)</div>
|
||||
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/1.9/portalcustom.html" class="wikilink1" title="documentation:1.9:portalcustom">portal customization</a>)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -114,7 +114,7 @@ As LDAP is a login/password based module, the authentication level can be:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
List of attributes to query to fill user session. See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
List of attributes to query to fill user session. See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -212,11 +212,11 @@ And the mail filter is:
|
|||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Password modify extended operation</strong>: enable to use the LDAP extended operation <code>password modify</code> instead of standard modify operation.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Change as user</strong>: enable to perform password modification with credentials of connected user. This requires to request user old password (see <a href="../../documentation/2.0/portalcustom.html" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>).</div>
|
||||
<li class="level1"><div class="li"> <strong>Change as user</strong>: enable to perform password modification with credentials of connected user. This requires to request user old password (see <a href="../../documentation/1.9/portalcustom.html" class="wikilink1" title="documentation:1.9:portalcustom">portal customization</a>).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>LDAP password encoding</strong>: can allow to manage old LDAP servers using specific encoding for passwords (default: utf-8).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Use reset attribute</strong>: enable to use the password reset attribute. This attribute is set by LemonLDAP::NG when <a href="../../documentation/2.0/resetpassword.html" class="wikilink1" title="documentation:2.0:resetpassword">password was reset by mail</a> and the user choose to generate the password (default: enabled).</div>
|
||||
<li class="level1"><div class="li"> <strong>Use reset attribute</strong>: enable to use the password reset attribute. This attribute is set by LemonLDAP::NG when <a href="../../documentation/1.9/resetpassword.html" class="wikilink1" title="documentation:1.9:resetpassword">password was reset by mail</a> and the user choose to generate the password (default: enabled).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Reset attribute</strong>: name of password reset attribute (default: pwdReset).</div>
|
||||
</li>
|
||||
|
|
@ -227,11 +227,11 @@ And the mail filter is:
|
|||
<p>
|
||||
<div class="row"><div class="col-md-6">
|
||||
<strong>Password expiration warning workflow</strong>
|
||||
<a href="/_detail/documentation/lemonldap-ng-password-expiration-warning.png?id=documentation%3A2.0%3Aauthldap" class="media" title="documentation:lemonldap-ng-password-expiration-warning.png"><img src="../../../media/documentation/lemonldap-ng-password-expiration-warning.png" class="media" alt="" /></a>
|
||||
<a href="/_detail/documentation/lemonldap-ng-password-expiration-warning.png?id=documentation%3A1.9%3Aauthldap" class="media" title="documentation:lemonldap-ng-password-expiration-warning.png"><img src="../../../media/documentation/lemonldap-ng-password-expiration-warning.png" class="media" alt="" /></a>
|
||||
</div>
|
||||
<div class="col-md-6">
|
||||
<strong>Password expiration workflow</strong>
|
||||
<a href="/_detail/documentation/lemonldap-ng-password-expired.png?id=documentation%3A2.0%3Aauthldap" class="media" title="documentation:lemonldap-ng-password-expired.png"><img src="../../../media/documentation/lemonldap-ng-password-expired.png" class="media" alt="" /></a>
|
||||
<a href="/_detail/documentation/lemonldap-ng-password-expired.png?id=documentation%3A1.9%3Aauthldap" class="media" title="documentation:lemonldap-ng-password-expired.png"><img src="../../../media/documentation/lemonldap-ng-password-expired.png" class="media" alt="" /></a>
|
||||
</div></div>
|
||||
</p>
|
||||
|
||||
|
|
@ -54,7 +54,8 @@ You have to use “Multi” as authentication module. This scheme expect a param
|
|||
<p>
|
||||
For example:
|
||||
</p>
|
||||
<pre class="code">Multi CAS;LDAP</pre>
|
||||
<pre class="code">Authentication => Multi
|
||||
Multi authentication stack => CAS;LDAP</pre>
|
||||
|
||||
<p>
|
||||
If <abbr title="Central Authentication Service">CAS</abbr> failed, LDAP will be used.
|
||||
|
|
@ -63,7 +64,7 @@ If <abbr title="Central Authentication Service">CAS</abbr> failed, LDAP will be
|
|||
<p>
|
||||
You can also add a condition. Example:
|
||||
</p>
|
||||
<pre class="code">Multi Remote $ENV{REMOTE_ADDR}=~/^192/;LDAP $ENV{REMOTE_ADDR}!~/^192/'</pre>
|
||||
<pre class="code">multiAuthStack => Remote $ENV{REMOTE_ADDR}=~/^192/;LDAP $ENV{REMOTE_ADDR}!~/^192/'</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">If Multi is used for authentication and user database, it will try to use the same module. Example, if you have “<abbr title="Database Interface">DBI</abbr>;LDAP” and <abbr title="Database Interface">DBI</abbr> failed for authentication, Multi will try first to call LDAP as user database.
|
||||
|
|
@ -71,7 +72,7 @@ You can also add a condition. Example:
|
|||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT4 SECTION "Configuration" [266-844] -->
|
||||
<!-- EDIT4 SECTION "Configuration" [266-916] -->
|
||||
<h3 class="sectionedit5" id="advanced_configuration">Advanced configuration</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -81,7 +82,7 @@ The “Multi” system can :
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> stack several times the same module with a different name</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> overload any <abbr title="LemonLDAP::NG">LL::NG</abbr> <a href="../../documentation/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter</a> when a specific backend is used</div>
|
||||
<li class="level1"><div class="li"> overload any <abbr title="LemonLDAP::NG">LL::NG</abbr> <a href="../../documentation/1.9/parameterlist.html" class="wikilink1" title="documentation:1.9:parameterlist">parameter</a> when a specific backend is used</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -93,19 +94,19 @@ The “Multi” system can :
|
|||
<p>
|
||||
To stack several times the same module, use “#name” with different names. Example:
|
||||
</p>
|
||||
<pre class="code">Multi LDAP#Openldap; LDAP#ActiveDirectory</pre>
|
||||
<pre class="code">multiAuthStack => LDAP#Openldap; LDAP#ActiveDirectory</pre>
|
||||
|
||||
<p>
|
||||
Then you can have different <a href="../../documentation/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameters</a> for each stored in a Perl hash entry named multi:
|
||||
Then you can have different <a href="../../documentation/1.9/parameterlist.html" class="wikilink1" title="documentation:1.9:parameterlist">parameters</a> for each stored in a Perl hash entry named multi:
|
||||
</p>
|
||||
<pre class="code perl">multi <span class="sy0">=></span> <span class="br0">{</span>
|
||||
<span class="st_h">'LDAP#Openldap'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
ldapServer <span class="sy0">=></span> <span class="st_h">'ldap1.example.com'</span><span class="sy0">,</span>
|
||||
LDAPFilter <span class="sy0">=></span> <span class="st_h">'(uid=$user)'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'ldapServer'</span> <span class="sy0">=></span> <span class="st_h">'ldap1.example.com'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAPFilter'</span> <span class="sy0">=></span> <span class="st_h">'(uid=$user)'</span><span class="sy0">,</span>
|
||||
<span class="br0">}</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAP#ActiveDirectory'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
ldapServer <span class="sy0">=></span> <span class="st_h">'ldaps://ad.example.com'</span><span class="sy0">,</span>
|
||||
LDAPFilter <span class="sy0">=></span> <span class="st_h">'(&(sAMAccountName=$user)(objectClass=person))'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'ldapServer'</span> <span class="sy0">=></span> <span class="st_h">'ldaps://ad.example.com'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAPFilter'</span> <span class="sy0">=></span> <span class="st_h">'(&(sAMAccountName=$user)(objectClass=person))'</span><span class="sy0">,</span>
|
||||
<span class="br0">}</span>
|
||||
<span class="br0">}</span><span class="sy0">,</span></pre>
|
||||
|
||||
|
|
@ -119,29 +120,29 @@ This key must be stored directly in portal index.pl file or in lemonldap-ng.ini:
|
|||
<pre class="code perl"><span class="kw1">my</span> <span class="re0">$portal</span> <span class="sy0">=</span> Lemonldap<span class="sy0">::</span><span class="me2">NG</span><span class="sy0">::</span><span class="me2">Portal</span><span class="sy0">::</span><span class="me2">SharedConf</span><span class="sy0">-></span><span class="kw2">new</span><span class="br0">(</span><span class="br0">{</span>
|
||||
multi <span class="sy0">=></span> <span class="br0">{</span>
|
||||
<span class="st_h">'LDAP#Openldap'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
ldapServer <span class="sy0">=></span> <span class="st_h">'ldap1.example.com'</span><span class="sy0">,</span>
|
||||
LDAPFilter <span class="sy0">=></span> <span class="st_h">'(uid=$user)'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'ldapServer'</span> <span class="sy0">=></span> <span class="st_h">'ldap1.example.com'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAPFilter'</span> <span class="sy0">=></span> <span class="st_h">'(uid=$user)'</span><span class="sy0">,</span>
|
||||
<span class="br0">}</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAP#ActiveDirectory'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
ldapServer <span class="sy0">=></span> <span class="st_h">'ldaps://ad.example.com'</span><span class="sy0">,</span>
|
||||
LDAPFilter <span class="sy0">=></span> <span class="st_h">'(&(sAMAccountName=$user)(objectClass=person))'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'ldapServer'</span> <span class="sy0">=></span> <span class="st_h">'ldaps://ad.example.com'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'LDAPFilter'</span> <span class="sy0">=></span> <span class="st_h">'(&(sAMAccountName=$user)(objectClass=person))'</span><span class="sy0">,</span>
|
||||
<span class="br0">}</span>
|
||||
<span class="br0">}</span><span class="sy0">,</span>
|
||||
<span class="br0">}</span><span class="br0">)</span></pre>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> or to use lemonldap-ng.ini, install it (one line only) in [portal] section:</div>
|
||||
<li class="level1"><div class="li"> or to use <code>lemonldap-ng.ini</code>, install it (one line only) in [portal] section:</div>
|
||||
</li>
|
||||
</ul>
|
||||
<pre class="code ini"><span class="re0"><span class="br0">[</span>portal<span class="br0">]</span></span>
|
||||
<span class="re1">multi</span> <span class="sy0">=</span><span class="re2"> <span class="br0">{</span>'LDAP#Openldap'<span class="sy0">=</span>><span class="br0">{</span>ldapServer<span class="sy0">=</span>>'ldap1.example.com',LDAPFilter<span class="sy0">=</span>>'<span class="br0">(</span>uid<span class="sy0">=</span>$user<span class="br0">)</span>'<span class="br0">}</span>,'LDAP#ActiveDirectory'<span class="sy0">=</span>><span class="br0">{</span>ldapServer<span class="sy0">=</span>>'ldaps://ad.example.com',LDAPFilter<span class="sy0">=</span>>'<span class="br0">(</span>&<span class="br0">(</span>sAMAccountName<span class="sy0">=</span>$user<span class="br0">)</span><span class="br0">(</span>objectClass<span class="sy0">=</span>person<span class="br0">)</span><span class="br0">)</span>'<span class="br0">}</span><span class="br0">}</span></span></pre>
|
||||
<span class="re1">multi</span> <span class="sy0">=</span><span class="re2"> <span class="br0">{</span>'LDAP#Openldap'<span class="sy0">=</span>><span class="br0">{</span>'ldapServer'<span class="sy0">=</span>>'ldap1.example.com','LDAPFilter'<span class="sy0">=</span>>'<span class="br0">(</span>uid<span class="sy0">=</span>$user<span class="br0">)</span>'<span class="br0">}</span>,'LDAP#ActiveDirectory'<span class="sy0">=</span>><span class="br0">{</span>'ldapServer'<span class="sy0">=</span>>'ldaps://ad.example.com','LDAPFilter'<span class="sy0">=</span>>'<span class="br0">(</span>&<span class="br0">(</span>sAMAccountName<span class="sy0">=</span>$user<span class="br0">)</span><span class="br0">(</span>objectClass<span class="sy0">=</span>person<span class="br0">)</span><span class="br0">)</span>'<span class="br0">}</span><span class="br0">}</span></span></pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT5 SECTION "Advanced configuration" [845-2447] -->
|
||||
<!-- EDIT5 SECTION "Advanced configuration" [917-2560] -->
|
||||
<h2 class="sectionedit6" id="known_problems">Known problems</h2>
|
||||
<div class="level2">
|
||||
|
||||
</div>
|
||||
<!-- EDIT6 SECTION "Known problems" [2448-2475] -->
|
||||
<!-- EDIT6 SECTION "Known problems" [2561-2588] -->
|
||||
<h3 class="sectionedit7" id="authapache_authentication">AuthApache authentication</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -150,11 +151,11 @@ When using this module, <abbr title="LemonLDAP::NG">LL::NG</abbr> portal will be
|
|||
</p>
|
||||
|
||||
<p>
|
||||
To bypass this, follow the documentation of <a href="../../documentation/2.0/authapache.html#use_kerberos_with_multiple_authentication_backend" class="wikilink1" title="documentation:2.0:authapache">AuthApache module</a>
|
||||
To bypass this, follow the documentation of <a href="../../documentation/1.9/authapache.html#use_kerberos_with_multiple_authentication_backend" class="wikilink1" title="documentation:1.9:authapache">AuthApache module</a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT7 SECTION "AuthApache authentication" [2476-2840] -->
|
||||
<!-- EDIT7 SECTION "AuthApache authentication" [2589-2953] -->
|
||||
<h3 class="sectionedit8" id="ssl_authentication">SSL authentication</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
</table></div>
|
||||
<!-- EDIT2 TABLE [22-85] -->
|
||||
<p>
|
||||
<p><div class="notewarning">OpenID protocol is deprecated. You should now use <a href="../../documentation/2.0/authopenidconnect.html" class="wikilink1" title="documentation:2.0:authopenidconnect">OpenID Connect</a>.
|
||||
<p><div class="notewarning">OpenID protocol is deprecated. You should now use <a href="../../documentation/1.9/authopenidconnect.html" class="wikilink1" title="documentation:1.9:authopenidconnect">OpenID Connect</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -48,7 +48,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/2.0/idpopenid.html" class="wikilink1" title="documentation:2.0:idpopenid">OpenID server</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/1.9/idpopenid.html" class="wikilink1" title="documentation:1.9:idpopenid">OpenID server</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -57,7 +57,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">OpenID authentication can proposed as an alternate authentication scheme using the <a href="../../documentation/2.0/authchoice.html" class="wikilink1" title="documentation:2.0:authchoice">authentication choice</a> method.
|
||||
<p><div class="notetip">OpenID authentication can proposed as an alternate authentication scheme using the <a href="../../documentation/1.9/authchoice.html" class="wikilink1" title="documentation:1.9:authchoice">authentication choice</a> method.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -127,7 +127,7 @@ To configure requested attributes, edit <strong>Exported variables</strong> and
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -78,7 +78,7 @@ As an RP, <abbr title="LemonLDAP::NG">LL::NG</abbr> supports a lot of OpenID Con
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <a href="../../documentation/2.0/openidconnectservice.html" class="wikilink1" title="documentation:2.0:openidconnectservice">OpenIDConnect service</a> configuration chapter.
|
||||
See <a href="../../documentation/1.9/openidconnectservice.html" class="wikilink1" title="documentation:1.9:openidconnectservice">OpenIDConnect service</a> configuration chapter.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -97,7 +97,7 @@ In <code>General Parameters</code> > <code>Authentication modules</code>, set
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">As passwords will not be managed by <abbr title="LemonLDAP::NG">LL::NG</abbr>, you can disable <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0:portalmenu">menu password module</a>.
|
||||
<p><div class="notetip">As passwords will not be managed by <abbr title="LemonLDAP::NG">LL::NG</abbr>, you can disable <a href="../../documentation/1.9/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.9:portalmenu">menu password module</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ To know this information, just take the portal <abbr title="Uniform Resource Loc
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If you use the <a href="../../documentation/2.0/authchoice.html" class="wikilink1" title="documentation:2.0:authchoice">choice backend</a>, you need to add the choice parameter in redirect <abbr title="Uniform Resource Locator">URL</abbr>
|
||||
<p><div class="noteimportant">If you use the <a href="../../documentation/1.9/authchoice.html" class="wikilink1" title="documentation:1.9:authchoice">choice backend</a>, you need to add the choice parameter in redirect <abbr title="Uniform Resource Locator">URL</abbr>
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -43,7 +43,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
The difference with <a href="../../documentation/2.0/authremote.html" class="wikilink1" title="documentation:2.0:authremote">remote authentication</a> is that the client will never be redirect to the main <abbr title="LemonLDAP::NG">LL::NG</abbr> portal. This configuration is usable if you want to expose your internal <abbr title="Single Sign On">SSO</abbr> portal to another network (DMZ).
|
||||
The difference with <a href="../../documentation/1.9/authremote.html" class="wikilink1" title="documentation:1.9:authremote">remote authentication</a> is that the client will never be redirect to the main <abbr title="LemonLDAP::NG">LL::NG</abbr> portal. This configuration is usable if you want to expose your internal <abbr title="Single Sign On">SSO</abbr> portal to another network (DMZ).
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -78,7 +78,7 @@ Then, go in <code>Proxy parameters</code>:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
The portal must be configured to accept SOAP authentication requests. See <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a> documentation.
|
||||
The portal must be configured to accept SOAP authentication requests. See <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP session backend</a> documentation.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -34,7 +34,7 @@
|
|||
</table></div>
|
||||
<!-- EDIT2 TABLE [23-86] -->
|
||||
<p>
|
||||
<p><div class="notewarning">This module is a <abbr title="LemonLDAP::NG">LL::NG</abbr> specific identity federation protocol. You may rather use standards protocols like <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML</a>, <a href="../../documentation/2.0/idpopenidconnect.html" class="wikilink1" title="documentation:2.0:idpopenidconnect">OpenID Connect</a> or <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS</a>.
|
||||
<p><div class="notewarning">This module is a <abbr title="LemonLDAP::NG">LL::NG</abbr> specific identity federation protocol. You may rather use standards protocols like <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML</a>, <a href="../../documentation/1.9/idpopenidconnect.html" class="wikilink1" title="documentation:1.9:idpopenidconnect">OpenID Connect</a> or <a href="../../documentation/1.9/idpcas.html" class="wikilink1" title="documentation:1.9:idpcas">CAS</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -45,14 +45,14 @@
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> The main portal is configured to use <abbr title="Cross Domain Authentication">CDA</abbr>. The secondary portal is declared in the Manager of the main <abbr title="LemonLDAP::NG">LL::NG</abbr> structure (else user will be rejected).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> The portal of the secondary <abbr title="LemonLDAP::NG">LL::NG</abbr> structure is configured to delegate authentication to a remote portal. A request to the main session database is done (trough <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a>) to be sure that the session exists.</div>
|
||||
<li class="level1"><div class="li"> The portal of the secondary <abbr title="LemonLDAP::NG">LL::NG</abbr> structure is configured to delegate authentication to a remote portal. A request to the main session database is done (trough <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP session backend</a>) to be sure that the session exists.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> If <code>exportedAttr</code> is set, only those attributes are copied in the session database of the secondary <abbr title="LemonLDAP::NG">LL::NG</abbr> structure. Else, all data are copied in the session database.</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/remote-principle.png?id=documentation%3A2.0%3Aauthremote" class="media" title="documentation:remote-principle.png"><img src="../../../media/documentation/remote-principle.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/remote-principle.png?id=documentation%3A1.9%3Aauthremote" class="media" title="documentation:remote-principle.png"><img src="../../../media/documentation/remote-principle.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
<ol>
|
||||
<li class="level1"><div class="li"> User tries to access to an application in the secondary <abbr title="LemonLDAP::NG">LL::NG</abbr> structure without having a session in this area</div>
|
||||
|
|
@ -115,11 +115,11 @@ Then, go in <code>Remote parameters</code>:
|
|||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Cookie name</strong> (optional): name of the cookie of primary portal, if different from secondary portal</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Sessions module</strong>: set <code>Lemonldap::NG::Common::Apache::Session::SOAP</code> for <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a>.</div>
|
||||
<li class="level1"><div class="li"> <strong>Sessions module</strong>: set <code>Lemonldap::NG::Common::Apache::Session::SOAP</code> for <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP session backend</a>.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Sessions module options</strong>:</div>
|
||||
<ul>
|
||||
<li class="level2"><div class="li"> <strong>proxy</strong>: SOAP sessions end point (see <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a> documentation)</div>
|
||||
<li class="level2"><div class="li"> <strong>proxy</strong>: SOAP sessions end point (see <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP session backend</a> documentation)</div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
@ -151,7 +151,7 @@ So on each main portal, internal users can access normally, and users issued fro
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/remote-interoperability.png?id=documentation%3A2.0%3Aauthremote" class="media" title="documentation:remote-interoperability.png"><img src="../../../media/documentation/remote-interoperability.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/remote-interoperability.png?id=documentation%3A1.9%3Aauthremote" class="media" title="documentation:remote-interoperability.png"><img src="../../../media/documentation/remote-interoperability.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
<ol>
|
||||
<li class="level1"><div class="li"> One user tries to access to the portal</div>
|
||||
|
|
@ -51,7 +51,7 @@ For each IDP, you can configure attributes that are collected. Some can be manda
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML IDP</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
<p><div class="notetip"><abbr title="LemonLDAP::NG">LL::NG</abbr> can also act as <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML IDP</a>, that allows to interconnect two <abbr title="LemonLDAP::NG">LL::NG</abbr> systems.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ For each IDP, you can configure attributes that are collected. Some can be manda
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service</a> configuration chapter.
|
||||
See <a href="../../documentation/1.9/samlservice.html" class="wikilink1" title="documentation:1.9:samlservice">SAML service</a> configuration chapter.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -85,7 +85,7 @@ In <code>General Parameters</code> > <code>Authentication modules</code>, set
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">As passwords will not be managed by <abbr title="LemonLDAP::NG">LL::NG</abbr>, you can disable <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0:portalmenu">menu password module</a>.
|
||||
<p><div class="notetip">As passwords will not be managed by <abbr title="LemonLDAP::NG">LL::NG</abbr>, you can disable <a href="../../documentation/1.9/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.9:portalmenu">menu password module</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -112,7 +112,7 @@ In the Manager, select node <code><abbr title="Security Assertion Markup Languag
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-saml-idp-new.png?id=documentation%3A2.0%3Aauthsaml" class="media" title="documentation:manager-saml-idp-new.png"><img src="../../../media/documentation/manager-saml-idp-new.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-saml-idp-new.png?id=documentation%3A1.9%3Aauthsaml" class="media" title="documentation:manager-saml-idp-new.png"><img src="../../../media/documentation/manager-saml-idp-new.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -124,7 +124,7 @@ Now you have access to the IDP parameters list:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-saml-idp-list.png?id=documentation%3A2.0%3Aauthsaml" class="media" title="documentation:manager-saml-idp-list.png"><img src="../../../media/documentation/manager-saml-idp-list.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-saml-idp-list.png?id=documentation%3A1.9%3Aauthsaml" class="media" title="documentation:manager-saml-idp-list.png"><img src="../../../media/documentation/manager-saml-idp-list.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -137,7 +137,7 @@ You must register IDP metadata here. You can do it either by uploading the file,
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-saml-idp-metadata.png?id=documentation%3A2.0%3Aauthsaml" class="media" title="documentation:manager-saml-idp-metadata.png"><img src="../../../media/documentation/manager-saml-idp-metadata.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-saml-idp-metadata.png?id=documentation%3A1.9%3Aauthsaml" class="media" title="documentation:manager-saml-idp-metadata.png"><img src="../../../media/documentation/manager-saml-idp-metadata.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -167,7 +167,7 @@ For each attribute, you can set:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-saml-idp-attribute.png?id=documentation%3A2.0%3Aauthsaml" class="media" title="documentation:manager-saml-idp-attribute.png"><img src="../../../media/documentation/manager-saml-idp-attribute.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-saml-idp-attribute.png?id=documentation%3A1.9%3Aauthsaml" class="media" title="documentation:manager-saml-idp-attribute.png"><img src="../../../media/documentation/manager-saml-idp-attribute.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -204,7 +204,7 @@ For example, to preselect this IDP for users coming from 129.168.0.0/16 network:
|
|||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Allow login from IDP</strong>: allow a user to connect directly from an IDP link. In this case, authentication is not a response to an issued authentication request, and we have less control on conditions.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Requested authentication context</strong>: this context is declared in authentication request. When receiving the request, the real authentication context will be mapped ton an internal authentication level (see <a href="../../documentation/2.0/samlservice.html#authentication_contexts" class="wikilink1" title="documentation:2.0:samlservice">how configure the mapping</a>), that you can check to allow or deny session creation.</div>
|
||||
<li class="level1"><div class="li"> <strong>Requested authentication context</strong>: this context is declared in authentication request. When receiving the request, the real authentication context will be mapped ton an internal authentication level (see <a href="../../documentation/1.9/samlservice.html#authentication_contexts" class="wikilink1" title="documentation:1.9:samlservice">how configure the mapping</a>), that you can check to allow or deny session creation.</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -225,7 +225,7 @@ For example, to preselect this IDP for users coming from 129.168.0.0/16 network:
|
|||
<div class="level5">
|
||||
|
||||
<p>
|
||||
These options override service signature options (see <a href="../../documentation/2.0/samlservice.html#general_options" class="wikilink1" title="documentation:2.0:samlservice">SAML service configuration</a>).
|
||||
These options override service signature options (see <a href="../../documentation/1.9/samlservice.html#general_options" class="wikilink1" title="documentation:1.9:samlservice">SAML service configuration</a>).
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Sign <abbr title="Single Sign On">SSO</abbr> message</strong>: sign <abbr title="Single Sign On">SSO</abbr> message</div>
|
||||
|
|
@ -91,7 +91,7 @@ You have then to declare HTTP headers exported by the main <abbr title="Single S
|
|||
</table></div>
|
||||
<!-- EDIT5 TABLE [1290-1392] -->
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -39,7 +39,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<abbr title="LemonLDAP::NG">LL::NG</abbr> uses <a href="http://httpd.apache.org/docs/current/mod/mod_ssl.html" class="urlextern" title="http://httpd.apache.org/docs/current/mod/mod_ssl.html" rel="nofollow">Apache SSL module</a>, like any other <a href="../../documentation/2.0/authapache.html" class="wikilink1" title="documentation:2.0:authapache">Apache authentication module</a>, with extra features:
|
||||
<abbr title="LemonLDAP::NG">LL::NG</abbr> uses <a href="http://httpd.apache.org/docs/current/mod/mod_ssl.html" class="urlextern" title="http://httpd.apache.org/docs/current/mod/mod_ssl.html" rel="nofollow">Apache SSL module</a>, like any other <a href="../../documentation/1.9/authapache.html" class="wikilink1" title="documentation:1.9:authapache">Apache authentication module</a>, with extra features:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Choice of any certificate attribute as user main login</div>
|
||||
|
|
@ -136,7 +136,7 @@ All SSL options are documented in <a href="http://httpd.apache.org/docs/current/
|
|||
Here are the main options used by <abbr title="LemonLDAP::NG">LL::NG</abbr>:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>SSLVerifyClient</strong>: set to <code>optional</code> to allow user with a bad certificate to access to <abbr title="LemonLDAP::NG">LL::NG</abbr> portal page. To switch to another authentication backend, use the <a href="../../documentation/2.0/authmulti.html" class="wikilink1" title="documentation:2.0:authmulti">Multi</a> module, for example: <code>Multi SSL;LDAP</code></div>
|
||||
<li class="level1"><div class="li"> <strong>SSLVerifyClient</strong>: set to <code>optional</code> to allow user with a bad certificate to access to <abbr title="LemonLDAP::NG">LL::NG</abbr> portal page. To switch to another authentication backend, use the <a href="../../documentation/1.9/authmulti.html" class="wikilink1" title="documentation:1.9:authmulti">Multi</a> module, for example: <code>Multi SSL;LDAP</code></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>SSLOptions</strong>: set to <code>+StdEnvVars</code> to get certificate fields in environment variables</div>
|
||||
</li>
|
||||
|
|
@ -78,7 +78,7 @@ If you use WebID as user database, declare values in <strong>exported variables<
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
|
||||
See also <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -88,7 +88,7 @@ The following table list fields to index depending on the feature you want to in
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
You can use Redis and set up the database like explained in <a href="../../documentation/2.0/nosqlsessionbackend.html" class="wikilink1" title="documentation:2.0:nosqlsessionbackend">Redis session backend</a>.
|
||||
You can use Redis and set up the database like explained in <a href="../../documentation/1.9/nosqlsessionbackend.html" class="wikilink1" title="documentation:1.9:nosqlsessionbackend">Redis session backend</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -127,7 +127,7 @@ You then just have to add the <code>Index</code> parameter in <code>General par
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Database must be prepared exactly like in <a href="../../documentation/2.0/sqlsessionbackend.html#prepare_the_database" class="wikilink1" title="documentation:2.0:sqlsessionbackend">SQL session backend</a> except that a field must be added for each data to index.
|
||||
Database must be prepared exactly like in <a href="../../documentation/1.9/sqlsessionbackend.html#prepare_the_database" class="wikilink1" title="documentation:1.9:sqlsessionbackend">SQL session backend</a> except that a field must be added for each data to index.
|
||||
</p>
|
||||
<pre class="code file sql"><span class="kw1">CREATE</span> <span class="kw1">TABLE</span> sessions <span class="br0">(</span>
|
||||
id <span class="kw1">CHAR</span><span class="br0">(</span><span class="nu0">32</span><span class="br0">)</span> <span class="kw1">NOT</span> <span class="kw1">NULL</span> <span class="kw1">PRIMARY</span> <span class="kw1">KEY</span><span class="sy0">,</span>
|
||||
|
|
@ -189,7 +189,7 @@ For databases like PostgreSQL, don't forget to add “Commit” with a valu
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Go in the Manager and set the session module to <code>Apache::Session::Browseable::LDAP</code>. Then configure the options like in <a href="../../documentation/2.0/ldapsessionbackend.html" class="wikilink1" title="documentation:2.0:ldapsessionbackend">LDAP session backend</a>.
|
||||
Go in the Manager and set the session module to <code>Apache::Session::Browseable::LDAP</code>. Then configure the options like in <a href="../../documentation/1.9/ldapsessionbackend.html" class="wikilink1" title="documentation:1.9:ldapsessionbackend">LDAP session backend</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -49,7 +49,7 @@ We use the Perl module Authen::Captcha to generate codes and images, which look
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/captcha.png?id=documentation%3A2.0%3Acaptcha" class="media" title="documentation:captcha.png"><img src="../../../media/documentation/captcha.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/captcha.png?id=documentation%3A1.9%3Acaptcha" class="media" title="documentation:captcha.png"><img src="../../../media/documentation/captcha.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -71,13 +71,13 @@ The <code>convertConfig</code> utility reads 2 <abbr title="LemonLDAP::NG">LL::N
|
|||
Documentation is available for configuration backends :
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">SQL</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/sqlconfbackend.html" class="wikilink1" title="documentation:1.9:sqlconfbackend">SQL</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/fileconfbackend.html" class="wikilink1" title="documentation:1.9:fileconfbackend">File</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/ldapconfbackend.html" class="wikilink1" title="documentation:1.9:ldapconfbackend">LDAP</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP proxy mechanism</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP proxy mechanism</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -43,16 +43,16 @@ LemonLDAP::NG configuration is stored in a backend that allows all modules to ac
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
Detailled configuration backends documentation is available <a href="../../documentation/2.0/start.html#configuration_database" class="wikilink1" title="documentation:2.0:start">here</a>.
|
||||
Detailled configuration backends documentation is available <a href="../../documentation/1.9/start.html#configuration_database" class="wikilink1" title="documentation:1.9:start">here</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
By default, configuration is stored in <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">files</a>, so access trough network is not possible. To allow this, use <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP</a> for configuration access, or use a network service like <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">SQL database</a> or <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP directory</a>.
|
||||
By default, configuration is stored in <a href="../../documentation/1.9/fileconfbackend.html" class="wikilink1" title="documentation:1.9:fileconfbackend">files</a>, so access trough network is not possible. To allow this, use <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP</a> for configuration access, or use a network service like <a href="../../documentation/1.9/sqlconfbackend.html" class="wikilink1" title="documentation:1.9:sqlconfbackend">SQL database</a> or <a href="../../documentation/1.9/ldapconfbackend.html" class="wikilink1" title="documentation:1.9:ldapconfbackend">LDAP directory</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Configuration backend can be set in the <a href="#local_file" title="documentation:2.0:configlocation ↵" class="wikilink1">local configuration file</a>, in <code>configuration</code> section.
|
||||
Configuration backend can be set in the <a href="#local_file" title="documentation:1.9:configlocation ↵" class="wikilink1">local configuration file</a>, in <code>configuration</code> section.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -63,7 +63,7 @@ For example, to configure the <code>File</code> configuration backend:
|
|||
<span class="re1">dirName</span> <span class="sy0">=</span><span class="re2"> /usr/local/lemonldap-ng/data/conf</span></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">See <a href="../../documentation/2.0/changeconfbackend.html" class="wikilink1" title="documentation:2.0:changeconfbackend">How to change configuration backend</a> to known how to change this.
|
||||
<p><div class="notetip">See <a href="../../documentation/1.9/changeconfbackend.html" class="wikilink1" title="documentation:1.9:changeconfbackend">How to change configuration backend</a> to known how to change this.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ If you can not access the Manager anymore, you can unprotect it by editing <code
|
|||
# * none : no protection</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">See <a href="../../documentation/2.0/managerprotection.html" class="wikilink1" title="documentation:2.0:managerprotection">Manager protection documentation</a> to know how to use Apache modules or <abbr title="LemonLDAP::NG">LL::NG</abbr> to manage access to Manager.
|
||||
<p><div class="notetip">See <a href="../../documentation/1.9/managerprotection.html" class="wikilink1" title="documentation:1.9:managerprotection">Manager protection documentation</a> to know how to use Apache modules or <abbr title="LemonLDAP::NG">LL::NG</abbr> to manage access to Manager.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -542,7 +542,7 @@ For example, to override configured skin for portal:
|
|||
<span class="re1">portalSkin</span> <span class="sy0">=</span><span class="re2"> dark</span></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">You need to know the technical name of configuration parameter to do this. You can refer to <a href="../../documentation/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter list</a> to find it.
|
||||
<p><div class="notetip">You need to know the technical name of configuration parameter to do this. You can refer to <a href="../../documentation/1.9/parameterlist.html" class="wikilink1" title="documentation:1.9:parameterlist">parameter list</a> to find it.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -556,7 +556,7 @@ LemonLDAP::NG allows to override any configuration parameter directly in script
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">You also need to know the technical name of configuration parameter to do this. You can refer to <a href="../../documentation/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter list</a> to find it.
|
||||
<p><div class="notetip">You also need to know the technical name of configuration parameter to do this. You can refer to <a href="../../documentation/1.9/parameterlist.html" class="wikilink1" title="documentation:1.9:parameterlist">parameter list</a> to find it.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ LemonLDAP::NG configuration is build around Apache virtual hosts. Each virtual h
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
To protect a virtual host in Apache, the LemonLDAP::NG Handler must be activated (see <a href="../../documentation/2.0/configlocation.html#apache" class="wikilink1" title="documentation:2.0:configlocation">Apache global configuration</a>).
|
||||
To protect a virtual host in Apache, the LemonLDAP::NG Handler must be activated (see <a href="../../documentation/1.9/configlocation.html#apache" class="wikilink1" title="documentation:1.9:configlocation">Apache global configuration</a>).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -110,12 +110,12 @@ To learn more about using Apache as reverse-proxy, see <a href="http://httpd.apa
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">Some applications need the <code>REMOTE_USER</code> environment variable to get the connected user, which is not set in reverse-proxy mode. In this case, see <a href="../../documentation/2.0/header_remote_user_conversion.html" class="wikilink1" title="documentation:2.0:header_remote_user_conversion">how convert header into environment variable</a>.
|
||||
<p><div class="notetip">Some applications need the <code>REMOTE_USER</code> environment variable to get the connected user, which is not set in reverse-proxy mode. In this case, see <a href="../../documentation/1.9/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.9:header_remote_user_conversion">how convert header into environment variable</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">You can also use the <a href="../../documentation/2.0/internalproxy.html" class="wikilink1" title="documentation:2.0:internalproxy">internal proxy</a> to replace Apache mod_proxy configuration.
|
||||
<p><div class="notetip">You can also use the <a href="../../documentation/1.9/internalproxy.html" class="wikilink1" title="documentation:1.9:internalproxy">internal proxy</a> to replace Apache mod_proxy configuration.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -169,7 +169,7 @@ A virtual host contains:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <strong><a href="../../documentation/2.0/writingrulesand_headers.html" class="wikilink1" title="documentation:2.0:writingrulesand_headers">Writing rules and headers</a></strong> to learn how to configure access control and HTTP headers sent to application by <abbr title="LemonLDAP::NG">LL::NG</abbr>.
|
||||
See <strong><a href="../../documentation/1.9/writingrulesand_headers.html" class="wikilink1" title="documentation:1.9:writingrulesand_headers">Writing rules and headers</a></strong> to learn how to configure access control and HTTP headers sent to application by <abbr title="LemonLDAP::NG">LL::NG</abbr>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -178,7 +178,7 @@ See <strong><a href="../../documentation/2.0/writingrulesand_headers.html" class
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <strong><a href="../../documentation/2.0/formreplay.html" class="wikilink1" title="documentation:2.0:formreplay">Form replay</a></strong> to learn how to configure form replay to POST data on protected applications.
|
||||
See <strong><a href="../../documentation/1.9/formreplay.html" class="wikilink1" title="documentation:1.9:formreplay">Form replay</a></strong> to learn how to configure form replay to POST data on protected applications.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
Custom functions allow to extend <abbr title="LemonLDAP::NG">LL::NG</abbr>, they can be used in <a href="../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a>, <a href="../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">rules</a> or <a href="../../documentation/2.0/formreplay.html" class="wikilink1" title="documentation:2.0:formreplay">form replay data</a>.
|
||||
Custom functions allow to extend <abbr title="LemonLDAP::NG">LL::NG</abbr>, they can be used in <a href="../../documentation/1.9/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.9:writingrulesand_headers">headers</a>, <a href="../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">rules</a> or <a href="../../documentation/1.9/formreplay.html" class="wikilink1" title="documentation:1.9:formreplay">form replay data</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -94,7 +94,7 @@ Go in Manager, <code>General Parameters</code> » <code>Advanced Parameters</cod
|
|||
<pre class="code">SSOExtensions::function1</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">If your function is not compliant with <a href="../../documentation/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail.
|
||||
<p><div class="noteimportant">If your function is not compliant with <a href="../../documentation/1.9/safejail.html" class="wikilink1" title="documentation:1.9:safejail">Safe jail</a>, you will need to disable the jail.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -40,7 +40,7 @@
|
|||
<pre class="file">Can't locate /usr/share/lemonldap-ng/configStorage.pl</pre>
|
||||
|
||||
<p>
|
||||
→ When you upgrade from Debian Lenny with customized index.pl files, you must upgrade them. See <a href="../../documentation/2.0/upgrade.html#debian_lenny_upgrade" class="wikilink1" title="documentation:2.0:upgrade">Debian Lenny upgrade</a>.
|
||||
→ When you upgrade from Debian Lenny with customized index.pl files, you must upgrade them. See <a href="../../documentation/1.9/upgrade.html#debian_lenny_upgrade" class="wikilink1" title="documentation:1.9:upgrade">Debian Lenny upgrade</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -29,7 +29,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Exported variables are the variables available to <a href="../../documentation/2.0/writingrulesand_headers.html" class="wikilink1" title="documentation:2.0:writingrulesand_headers">write rules and headers</a>. They are extracted from the users database by the <a href="../../documentation/2.0/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:2.0:start">users module</a>.
|
||||
Exported variables are the variables available to <a href="../../documentation/1.9/writingrulesand_headers.html" class="wikilink1" title="documentation:1.9:writingrulesand_headers">write rules and headers</a>. They are extracted from the users database by the <a href="../../documentation/1.9/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.9:start">users module</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -37,7 +37,7 @@ To create a variable, you've just to map a user attributes in <abbr title="
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Examples for <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP</a>:
|
||||
Examples for <a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP</a>:
|
||||
</p>
|
||||
<div class="table sectionedit3"><table class="inline">
|
||||
<thead>
|
||||
|
|
@ -66,7 +66,7 @@ You can define exported variables for each module in the module configuration it
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/exportedvars.png?id=documentation%3A2.0%3Aexportedvars" class="media" title="documentation:exportedvars.png"><img src="../../../media/documentation/exportedvars.png" class="mediacenter" title="Exported variables in the Manager" alt="Exported variables in the Manager" width="500" /></a>
|
||||
<a href="/_detail/documentation/exportedvars.png?id=documentation%3A1.9%3Aexportedvars" class="media" title="documentation:exportedvars.png"><img src="../../../media/documentation/exportedvars.png" class="mediacenter" title="Exported variables in the Manager" alt="Exported variables in the Manager" width="500" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -75,18 +75,35 @@ You can define exported variables for each module in the module configuration it
|
|||
<div class="level2">
|
||||
|
||||
</div>
|
||||
<div class="plugin_include_content" id="plugin_include__documentation:2.0:performances">
|
||||
<div class="plugin_include_content" id="plugin_include__documentation:1.9:performances">
|
||||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Macros and groups are calculated during authentication process by the portal:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> macros are used to extend (or rewrite) <span class="curid"><a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables</a></span>. A macro is stored as attributes: it can contain boolean results or any string</div>
|
||||
<li class="level1"><div class="li"> macros are used to extend (or rewrite) <span class="curid"><a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables</a></span>. A macro is stored as attributes: it can contain boolean results or any string</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> groups are stored as space-separated strings in the special attribute “groups”: it contains the names of groups whose rules were returned true for the current user</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> You can also get groups in <code>$hGroups</code> which is a Hash Reference of this form:</div>
|
||||
</li>
|
||||
</ul>
|
||||
<pre class="code perl"><span class="re0">$hGroups</span> <span class="sy0">=</span> <span class="br0">{</span>
|
||||
<span class="st_h">'group3'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
<span class="st_h">'description'</span> <span class="sy0">=></span> <span class="br0">[</span>
|
||||
<span class="st_h">'Service 3'</span><span class="sy0">,</span>
|
||||
<span class="st_h">'Service 3 TEST'</span>
|
||||
<span class="br0">]</span><span class="sy0">,</span>
|
||||
<span class="st_h">'cn'</span> <span class="sy0">=></span> <span class="br0">[</span>
|
||||
<span class="st_h">'group3'</span>
|
||||
<span class="br0">]</span><span class="sy0">,</span>
|
||||
<span class="st_h">'name'</span> <span class="sy0">=></span> <span class="st_h">'group3'</span>
|
||||
<span class="br0">}</span><span class="sy0">,</span>
|
||||
<span class="st_h">'admin'</span> <span class="sy0">=></span> <span class="br0">{</span>
|
||||
<span class="st_h">'name'</span> <span class="sy0">=></span> <span class="st_h">'admin'</span>
|
||||
<span class="br0">}</span>
|
||||
<span class="br0">}</span></pre>
|
||||
|
||||
<p>
|
||||
Example for macros:
|
||||
|
|
@ -108,14 +125,19 @@ Example for groups:
|
|||
admin <span class="sy0">-></span> <span class="re0">$uid</span> <span class="kw1">eq</span> <span class="st_h">'foo'</span> <span class="kw1">or</span> <span class="re0">$uid</span> <span class="kw1">eq</span> <span class="st_h">'bar'</span>
|
||||
|
||||
<span class="co1"># Use a group in a rule</span>
|
||||
<span class="sy0">^/</span>admin <span class="sy0">-></span> <span class="re0">$groups</span> <span class="sy0">=~</span> <span class="sy0">/</span><span class="re0">\badmin</span><span class="re0">\b</span><span class="sy0">/</span></pre>
|
||||
<span class="sy0">^/</span>admin <span class="sy0">-></span> <span class="re0">$groups</span> <span class="sy0">=~</span> <span class="co2">/\badmin\b/</span>
|
||||
|
||||
<span class="co1"># Or with hGroups</span>
|
||||
<span class="sy0">^/</span>admin <span class="sy0">-></span> <a href="http://perldoc.perl.org/functions/defined.html"><span class="kw3">defined</span></a> <span class="re0">$hGroups</span><span class="br0">{</span><span class="st_h">'admin'</span><span class="br0">}</span></pre>
|
||||
|
||||
<p>
|
||||
Note that groups are computed after macros, so a group rule may involve a macro value.
|
||||
<p><div class="noteclassic">Groups are computed after macros, so a group rule may involve a macro value.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Besides, macros and groups are computed in alphanumeric order, that is, in the order they are displayed in the manager. For example, macro “macro1” will be computed before macro “macro2”: so, expression of macro2 may involve value of macro1. As same for groups: a group rule may involve another, previously computed group.
|
||||
<p><div class="noteimportant">Macros and groups are computed in alphanumeric order, that is, in the order they are displayed in the manager. For example, macro “macro1” will be computed before macro “macro2”: so, expression of macro2 may involve value of macro1. As same for groups: a group rule may involve another, previously computed group.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -29,16 +29,16 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
When <a href="../../documentation/2.0/writingrulesand_headers.html" class="wikilink1" title="documentation:2.0:writingrulesand_headers">writing rules and headers</a>, you can use Perl expressions that will be evaluated in a jail, to prevent bad code execution.
|
||||
When <a href="../../documentation/1.9/writingrulesand_headers.html" class="wikilink1" title="documentation:1.9:writingrulesand_headers">writing rules and headers</a>, you can use Perl expressions that will be evaluated in a jail, to prevent bad code execution.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This is also true for:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0:portalmenu">Menu modules activation rules</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.9:portalmenu">Menu modules activation rules</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/formreplay.html" class="wikilink1" title="documentation:2.0:formreplay">Form replay data</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/formreplay.html" class="wikilink1" title="documentation:1.9:formreplay">Form replay data</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Macros</div>
|
||||
</li>
|
||||
|
|
@ -54,29 +54,29 @@ Inside this jail, you can access to:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> Core Perl subroutines (split, pop, map, etc.)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/customfunctions.html" class="wikilink1" title="documentation:2.0:customfunctions">Custom functions</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/customfunctions.html" class="wikilink1" title="documentation:1.9:customfunctions">Custom functions</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> The <a href="http://perldoc.perl.org/MIME/Base64.html" class="urlextern" title="http://perldoc.perl.org/MIME/Base64.html" rel="nofollow">encode_base64</a> subroutine</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Environment variables, in some cases (through %ENV)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="#request_informations" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">Informations about current request</a></div>
|
||||
<li class="level1"><div class="li"> <a href="#request_informations" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">Informations about current request</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="#extended_functions_list" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">Extended functions</a>:</div>
|
||||
<li class="level1"><div class="li"> <a href="#extended_functions_list" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">Extended functions</a>:</div>
|
||||
<ul>
|
||||
<li class="level2"><div class="li"> <a href="#date" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">date</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#date" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">date</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#checklogonhours" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">checkLogonHours</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#checklogonhours" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">checkLogonHours</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#checkdate" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">checkDate</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#checkdate" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">checkDate</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#basic" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">basic</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#basic" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">basic</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#unicode2iso" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">unicode2iso</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#unicode2iso" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">unicode2iso</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#iso2unicode" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">iso2unicode</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#iso2unicode" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">iso2unicode</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="#groupmatch" title="documentation:2.0:extendedfunctions ↵" class="wikilink1">groupMatch</a></div>
|
||||
<li class="level2"><div class="li"> <a href="#groupmatch" title="documentation:1.9:extendedfunctions ↵" class="wikilink1">groupMatch</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
@ -146,7 +146,7 @@ For example, for a full access, excepted week-end:
|
|||
<pre class="code">000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">The <a href="../../documentation/2.0/authldap.html#schema_extension" class="wikilink1" title="documentation:2.0:authldap">LDAP schema extension</a> can be used to store this value. You can also use the binary value from the logonHours attribute of Active Directory
|
||||
<p><div class="notetip">The <a href="../../documentation/1.9/authldap.html#schema_extension" class="wikilink1" title="documentation:1.9:authldap">LDAP schema extension</a> can be used to store this value. You can also use the binary value from the logonHours attribute of Active Directory
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -200,7 +200,7 @@ This function will check the date of current request, and compare it to a start
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">The <a href="../../documentation/2.0/authldap.html#schema_extension" class="wikilink1" title="documentation:2.0:authldap">LDAP schema extension</a> can be used to store these values
|
||||
<p><div class="notetip">The <a href="../../documentation/1.9/authldap.html#schema_extension" class="wikilink1" title="documentation:1.9:authldap">LDAP schema extension</a> can be used to store these values
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -232,12 +232,12 @@ Simple usage example:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.9/safejail.html" class="wikilink1" title="documentation:1.9:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This function builds the <code>Authorization</code> HTTP header used in <a href="../../documentation/2.0/applications/authbasic.html" class="wikilink1" title="documentation:2.0:applications:authbasic">HTTP Basic authentication scheme</a>. It will force conversion from UTF-8 to ISO-8859-1 of user and password data.
|
||||
This function builds the <code>Authorization</code> HTTP header used in <a href="../../documentation/1.9/applications/authbasic.html" class="wikilink1" title="documentation:1.9:applications:authbasic">HTTP Basic authentication scheme</a>. It will force conversion from UTF-8 to ISO-8859-1 of user and password data.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -261,7 +261,7 @@ Simple usage example:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.9/safejail.html" class="wikilink1" title="documentation:1.9:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -288,7 +288,7 @@ Simple usage example:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.9/safejail.html" class="wikilink1" title="documentation:1.9:safejail">Safe jail</a>, you will need to disable the jail to use it.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -41,11 +41,11 @@ So you can configure it to authenticate users using a federation protocol and si
|
|||
For example, a <abbr title="LemonLDAP::NG">LL::NG</abbr> server can be:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> A <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS server</a> with <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML authentication</a></div>
|
||||
<li class="level1"><div class="li"> A <a href="../../documentation/1.9/idpcas.html" class="wikilink1" title="documentation:1.9:idpcas">CAS server</a> with <a href="../../documentation/1.9/authsaml.html" class="wikilink1" title="documentation:1.9:authsaml">SAML authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> An <a href="../../documentation/2.0/idpopenid.html" class="wikilink1" title="documentation:2.0:idpopenid">OpenID server</a> with <a href="../../documentation/2.0/authcas.html" class="wikilink1" title="documentation:2.0:authcas">CAS authentication</a></div>
|
||||
<li class="level1"><div class="li"> An <a href="../../documentation/1.9/idpopenid.html" class="wikilink1" title="documentation:1.9:idpopenid">OpenID server</a> with <a href="../../documentation/1.9/authcas.html" class="wikilink1" title="documentation:1.9:authcas">CAS authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> An <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML server</a> with <a href="../../documentation/2.0/authopenid.html" class="wikilink1" title="documentation:2.0:authopenid">OpenID authentication</a></div>
|
||||
<li class="level1"><div class="li"> An <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML server</a> with <a href="../../documentation/1.9/authopenid.html" class="wikilink1" title="documentation:1.9:authopenid">OpenID authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> …</div>
|
||||
</li>
|
||||
|
|
@ -55,9 +55,9 @@ For example, a <abbr title="LemonLDAP::NG">LL::NG</abbr> server can be:
|
|||
See the following chapters:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:2.0:start">Authentication protocols</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.9:start">Authentication protocols</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#identity_provider" class="wikilink1" title="documentation:2.0:start">Identity provider</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#identity_provider" class="wikilink1" title="documentation:1.9:start">Identity provider</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ This is the default configuration backend. Configuration is stored as JSON.
|
|||
<p><div class="notetip">This configuration storage can be shared between different hosts using:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP configuration backend proxy</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP configuration backend proxy</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> any files sharing system (NFS, NAS, SAN,…)</div>
|
||||
</li>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
File session backend is the more simple session database. Sessions are stored as files in a single directory. Lock files are stored in another directory. It can not be used to share sessions between different servers except if you share directories (with NFS,…) or if you use <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP proxy</a>.
|
||||
File session backend is the more simple session database. Sessions are stored as files in a single directory. Lock files are stored in another directory. It can not be used to share sessions between different servers except if you share directories (with NFS,…) or if you use <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP proxy</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -38,7 +38,7 @@ This kind of <abbr title="Single Sign On">SSO</abbr> mechanism is not clean, and
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Please always try to find another solution to protect your application with <abbr title="LemonLDAP::NG">LL::NG</abbr>. At least, check if it is not a <a href="../../documentation/2.0/applications.html" class="wikilink1" title="documentation:2.0:applications">known application</a>, or <a href="../../documentation/2.0/selfmadeapplication.html" class="wikilink1" title="documentation:2.0:selfmadeapplication">try to adapt its source code</a>.
|
||||
Please always try to find another solution to protect your application with <abbr title="LemonLDAP::NG">LL::NG</abbr>. At least, check if it is not a <a href="../../documentation/1.9/applications.html" class="wikilink1" title="documentation:1.9:applications">known application</a>, or <a href="../../documentation/1.9/selfmadeapplication.html" class="wikilink1" title="documentation:1.9:selfmadeapplication">try to adapt its source code</a>.
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -53,7 +53,7 @@ POST data can be static values or computed from user's session.
|
|||
|
||||
<p>
|
||||
<p><div class="notetip">
|
||||
To post user's password, you must enable <a href="../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">password storing</a>. In this case you will be able to use <code>$_password</code> to fill any password POST field.
|
||||
To post user's password, you must enable <a href="../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">password storing</a>. In this case you will be able to use <code>$_password</code> to fill any password POST field.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ Then go in Manager, “Virtual Hosts” » <em>virtualhost</em> » “Form repla
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-formreplay-newurl.png?id=documentation%3A2.0%3Aformreplay" class="media" title="documentation:manager-formreplay-newurl.png"><img src="../../../media/documentation/manager-formreplay-newurl.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-formreplay-newurl.png?id=documentation%3A1.9%3Aformreplay" class="media" title="documentation:manager-formreplay-newurl.png"><img src="../../../media/documentation/manager-formreplay-newurl.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -141,7 +141,7 @@ Then click on <code>New POST data</code> and add all data with their values, for
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-formreplay-newdata.png?id=documentation%3A2.0%3Aformreplay" class="media" title="documentation:manager-formreplay-newdata.png"><img src="../../../media/documentation/manager-formreplay-newdata.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-formreplay-newdata.png?id=documentation%3A1.9%3Aformreplay" class="media" title="documentation:manager-formreplay-newdata.png"><img src="../../../media/documentation/manager-formreplay-newdata.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -52,7 +52,7 @@ This can be useful to allow an third party application to access a virtual host
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Configure the virtual host like other <a href="../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a> but use AuthBasic Handler instead of default Handler.
|
||||
Configure the virtual host like other <a href="../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">protected virtual host</a> but use AuthBasic Handler instead of default Handler.
|
||||
</p>
|
||||
<pre class="code file apache"><<span class="kw3">VirtualHost</span> *:<span class="nu0">80</span>>
|
||||
<span class="kw1">ServerName</span> basic.example.com
|
||||
|
|
@ -82,7 +82,7 @@ If LemonLDAP::NG portal is protected by SSL with a self-signed certificate, you
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
No parameters needed. But you have to allow sessions web services, see <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP sessions backend</a>.
|
||||
No parameters needed. But you have to allow sessions web services, see <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP sessions backend</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -70,7 +70,7 @@ Sometimes, PHP applications also check the PHP_AUTH_USER and PHP_AUHT_PW environ
|
|||
<span class="kw1">SetEnvIfNoCase</span> Auth-Password <span class="st0">"(.*)"</span> PHP_AUTH_PW=$1</pre>
|
||||
|
||||
<p>
|
||||
Of course, you need to <a href="../../documentation/2.0/passwordstore.html" class="wikilink1" title="documentation:2.0:passwordstore">store password in session</a> to fill PHP_AUTH_PW.
|
||||
Of course, you need to <a href="../../documentation/1.9/passwordstore.html" class="wikilink1" title="documentation:1.9:passwordstore">store password in session</a> to fill PHP_AUTH_PW.
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -38,7 +38,7 @@ You can for example set up a fail-over cluster with <a href="http://www.linux-ha
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/ha-apache.png?id=documentation%3A2.0%3Ahighavailability" class="media" title="documentation:ha-apache.png"><img src="../../../media/documentation/ha-apache.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/ha-apache.png?id=documentation%3A1.9%3Ahighavailability" class="media" title="documentation:ha-apache.png"><img src="../../../media/documentation/ha-apache.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -46,7 +46,7 @@ You just have to share configuration and sessions databases between those server
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/ha-sessions-configuration.png?id=documentation%3A2.0%3Ahighavailability" class="media" title="documentation:ha-sessions-configuration.png"><img src="../../../media/documentation/ha-sessions-configuration.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/ha-sessions-configuration.png?id=documentation%3A1.9%3Ahighavailability" class="media" title="documentation:ha-sessions-configuration.png"><img src="../../../media/documentation/ha-sessions-configuration.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
<abbr title="LemonLDAP::NG">LL::NG</abbr> can act as an <abbr title="Central Authentication Service">CAS</abbr> server, that can allow to federate <abbr title="LemonLDAP::NG">LL::NG</abbr> with:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/2.0/authcas.html" class="wikilink1" title="documentation:2.0:authcas">CAS authentication</a></div>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/1.9/authcas.html" class="wikilink1" title="documentation:1.9:authcas">CAS authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Any <abbr title="Central Authentication Service">CAS</abbr> consumer</div>
|
||||
</li>
|
||||
|
|
@ -53,7 +53,7 @@ In the Manager, go in <code>General Parameters</code> » <code>Issuer modules</c
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Activation</strong>: set to <code>On</code>.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/cas/</code> unless you have change <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a> file.</div>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/cas/</code> unless you have change <a href="../../documentation/1.9/configlocation.html#portal" class="wikilink1" title="documentation:1.9:configlocation">Apache portal configuration</a> file.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Use rule</strong>: a rule to allow user to use this module, set to 1 to always allow.</div>
|
||||
</li>
|
||||
|
|
@ -72,7 +72,7 @@ For example, to allow only users with a strong authentication level:
|
|||
|
||||
<p>
|
||||
<p><div class="noteimportant">
|
||||
Apache rewrite rules must have been activated in <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a>:
|
||||
Apache rewrite rules must have been activated in <a href="../../documentation/1.9/configlocation.html#portal" class="wikilink1" title="documentation:1.9:configlocation">Apache portal configuration</a>:
|
||||
</p>
|
||||
<pre class="code file apache"> <<span class="kw3">IfModule</span> mod_rewrite.c>
|
||||
<span class="kw1">RewriteEngine</span> <span class="kw2">On</span>
|
||||
|
|
@ -100,7 +100,7 @@ Then go in <code>Options</code> to define:
|
|||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong><abbr title="Central Authentication Service">CAS</abbr> session module name and options</strong>: choose a specific module if you do not want to mix <abbr title="Central Authentication Service">CAS</abbr> sessions and normal sessions (see <a href="../../documentation/2.0/samlservice.html#saml_sessions_module_name_and_options" class="wikilink1" title="documentation:2.0:samlservice">why</a>).</div>
|
||||
<li class="level1"><div class="li"> <strong><abbr title="Central Authentication Service">CAS</abbr> session module name and options</strong>: choose a specific module if you do not want to mix <abbr title="Central Authentication Service">CAS</abbr> sessions and normal sessions (see <a href="../../documentation/1.9/samlservice.html#saml_sessions_module_name_and_options" class="wikilink1" title="documentation:1.9:samlservice">why</a>).</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<p><div class="notewarning">OpenID protocol is deprecated, you should now use <a href="../../documentation/2.0/idpopenidconnect.html" class="wikilink1" title="documentation:2.0:idpopenidconnect">OpenID Connect</a>
|
||||
<p><div class="notewarning">OpenID protocol is deprecated, you should now use <a href="../../documentation/1.9/idpopenidconnect.html" class="wikilink1" title="documentation:1.9:idpopenidconnect">OpenID Connect</a>
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -37,7 +37,7 @@
|
|||
<abbr title="LemonLDAP::NG">LL::NG</abbr> can act as an OpenID 2.0 Server, that can allow to federate <abbr title="LemonLDAP::NG">LL::NG</abbr> with:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/2.0/authopenid.html" class="wikilink1" title="documentation:2.0:authopenid">OpenID authentication</a></div>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/1.9/authopenid.html" class="wikilink1" title="documentation:1.9:authopenid">OpenID authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Any OpenID consumer</div>
|
||||
</li>
|
||||
|
|
@ -53,7 +53,7 @@ When <abbr title="LemonLDAP::NG">LL::NG</abbr> is configured as OpenID identity
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> [PORTAL] is the portal <abbr title="Uniform Resource Locator">URL</abbr></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> [login] is the user login (or any other session information, <span class="curid"><a href="../../documentation/2.0/idpopenid.html#configuration" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>)</div>
|
||||
<li class="level1"><div class="li"> [login] is the user login (or any other session information, <span class="curid"><a href="../../documentation/1.9/idpopenid.html#configuration" class="wikilink1" title="documentation:1.9:idpopenid">see below</a></span>)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ In the Manager, go in <code>General Parameters</code> » <code>Issuer modules</c
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Activation</strong>: set to <code>On</code></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/openidserver/</code> unless you have change <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a> file.</div>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/openidserver/</code> unless you have change <a href="../../documentation/1.9/configlocation.html#portal" class="wikilink1" title="documentation:1.9:configlocation">Apache portal configuration</a> file.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Use rule</strong>: a rule to allow user to use this module, set to 1 to always allow.</div>
|
||||
</li>
|
||||
|
|
@ -92,7 +92,7 @@ For example, to allow only users with a strong authentication level:
|
|||
|
||||
<p>
|
||||
<p><div class="noteimportant">
|
||||
Apache rewrite rules must have been activated in <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a>:
|
||||
Apache rewrite rules must have been activated in <a href="../../documentation/1.9/configlocation.html#portal" class="wikilink1" title="documentation:1.9:configlocation">Apache portal configuration</a>:
|
||||
</p>
|
||||
<pre class="code file apache"> <<span class="kw3">IfModule</span> mod_rewrite.c>
|
||||
<span class="kw1">RewriteEngine</span> <span class="kw2">On</span>
|
||||
|
|
@ -108,13 +108,13 @@ Apache rewrite rules must have been activated in <a href="../../documentation/2.
|
|||
Then go in <code>Options</code> to define:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Secret token</strong>: a secret token used to secure transmissions between OpenID client and server (<span class="curid"><a href="../../documentation/2.0/idpopenid.html#security" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>).</div>
|
||||
<li class="level1"><div class="li"> <strong>Secret token</strong>: a secret token used to secure transmissions between OpenID client and server (<span class="curid"><a href="../../documentation/1.9/idpopenid.html#security" class="wikilink1" title="documentation:1.9:idpopenid">see below</a></span>).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>OpenID login</strong>: the session key used to match OpenID login.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Authorized domains</strong>: white list or black list of OpenID client domains (<span class="curid"><a href="../../documentation/2.0/idpopenid.html#security" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>).</div>
|
||||
<li class="level1"><div class="li"> <strong>Authorized domains</strong>: white list or black list of OpenID client domains (<span class="curid"><a href="../../documentation/1.9/idpopenid.html#security" class="wikilink1" title="documentation:1.9:idpopenid">see below</a></span>).</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>SREG mapping</strong>: link between SREG attributes and session keys (<span class="curid"><a href="../../documentation/2.0/idpopenid.html#shared_attributes_sreg" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>).</div>
|
||||
<li class="level1"><div class="li"> <strong>SREG mapping</strong>: link between SREG attributes and session keys (<span class="curid"><a href="../../documentation/1.9/idpopenid.html#shared_attributes_sreg" class="wikilink1" title="documentation:1.9:idpopenid">see below</a></span>).</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -173,7 +173,7 @@ Each SREG attribute will be associated to a user session key. A session key can
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">Note that <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML</a> protocol is more secured than OpenID, so when your partners are known, prefer <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML</a>.
|
||||
<p><div class="noteimportant">Note that <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML</a> protocol is more secured than OpenID, so when your partners are known, prefer <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ As an OP, <abbr title="LemonLDAP::NG">LL::NG</abbr> supports a lot of OpenID Con
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <a href="../../documentation/2.0/openidconnectservice.html" class="wikilink1" title="documentation:2.0:openidconnectservice">OpenID Connect service</a> configuration chapter.
|
||||
See <a href="../../documentation/1.9/openidconnectservice.html" class="wikilink1" title="documentation:1.9:openidconnectservice">OpenID Connect service</a> configuration chapter.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -32,31 +32,31 @@
|
|||
<abbr title="LemonLDAP::NG">LL::NG</abbr> can act as an <abbr title="Security Assertion Markup Language">SAML</abbr> 2.0 Identity Provider, that can allow to federate <abbr title="LemonLDAP::NG">LL::NG</abbr> with:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML authentication</a></div>
|
||||
<li class="level1"><div class="li"> Another <abbr title="LemonLDAP::NG">LL::NG</abbr> system configured with <a href="../../documentation/1.9/authsaml.html" class="wikilink1" title="documentation:1.9:authsaml">SAML authentication</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Any <abbr title="Security Assertion Markup Language">SAML</abbr> Service Provider, for example:</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
<div class="plugin_include_content" id="plugin_include__documentation:2.0:applications">
|
||||
<div class="plugin_include_content" id="plugin_include__documentation:1.9:applications">
|
||||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<p><div class="noteclassic">This requires to configure <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <span class="curid"><a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></span>.
|
||||
<p><div class="noteclassic">This requires to configure <abbr title="LemonLDAP::NG">LL::NG</abbr> as an <span class="curid"><a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML Identity Provider</a></span>.
|
||||
</div></p>
|
||||
</p>
|
||||
<div class="table sectionedit3"><table class="inline">
|
||||
<thead>
|
||||
<tr class="row0 roweven">
|
||||
<th class="col0 centeralign"> Google Apps </th><th class="col1 centeralign"> Zimbra </th><th class="col2 centeralign"> SAP </th><th class="col3 centeralign"> Cornerstone </th><th class="col4"> SalesForce </th>
|
||||
<th class="col0 centeralign"> Google Apps </th><th class="col1 centeralign"> Zimbra </th><th class="col2 centeralign"> SAP </th><th class="col3 centeralign"> Cornerstone </th><th class="col4 centeralign"> SalesForce </th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0 centeralign"> <a href="../../documentation/2.0/applications/googleapps.html" class="media" title="documentation:2.0:applications:googleapps"><img src="../../../media/applications/googleapps_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="media" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" class="media" title="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td><td class="col3 rightalign"> <a href="../../documentation/2.0/applications/cornerstone.html" class="media" title="documentation:2.0:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 leftalign"> <a href="../../documentation/2.0/applications/salesforce.html" class="media" title="documentation:2.0:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
|
||||
<td class="col0 centeralign"> <a href="../../documentation/1.9/applications/googleapps.html" class="media" title="documentation:1.9:applications:googleapps"><img src="../../../media/applications/googleapps_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" class="media" title="http://blog.zimbra.com/blog/archives/2010/06/using-saml-assertions-to-access-zimbra.html" rel="nofollow"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" class="media" title="http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm" rel="nofollow"><img src="../../../media/applications/saplogo.gif" class="media" title="SAP" alt="SAP" /></a> </td><td class="col3 centeralign"> <a href="../../documentation/1.9/applications/cornerstone.html" class="media" title="documentation:1.9:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 centeralign"> <a href="../../documentation/1.9/applications/salesforce.html" class="media" title="documentation:1.9:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
|
||||
</tr>
|
||||
</table></div>
|
||||
<!-- EDIT3 TABLE [2729-3270] -->
|
||||
<!-- EDIT3 TABLE [2693-3238] -->
|
||||
</div>
|
||||
</div>
|
||||
<div class="level2">
|
||||
|
|
@ -72,7 +72,7 @@
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service</a> configuration chapter.
|
||||
See <a href="../../documentation/1.9/samlservice.html" class="wikilink1" title="documentation:1.9:samlservice">SAML service</a> configuration chapter.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -86,7 +86,7 @@ Go in <code>General Parameters</code> » <code>Issuer modules</code> » <code><a
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Activation</strong>: set to <code>On</code>.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/saml/</code> unless you have change <abbr title="Security Assertion Markup Language">SAML</abbr> end points suffix in <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service configuration</a>.</div>
|
||||
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/saml/</code> unless you have change <abbr title="Security Assertion Markup Language">SAML</abbr> end points suffix in <a href="../../documentation/1.9/samlservice.html" class="wikilink1" title="documentation:1.9:samlservice">SAML service configuration</a>.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Use rule</strong>: a rule to allow user to use this module, set to <code>1</code> to always allow.</div>
|
||||
</li>
|
||||
|
|
@ -126,7 +126,7 @@ In the Manager, select node <abbr title="Security Assertion Markup Language">SAM
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-saml-sp-new.png?id=documentation%3A2.0%3Aidpsaml" class="media" title="documentation:manager-saml-sp-new.png"><img src="../../../media/documentation/manager-saml-sp-new.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-saml-sp-new.png?id=documentation%3A1.9%3Aidpsaml" class="media" title="documentation:manager-saml-sp-new.png"><img src="../../../media/documentation/manager-saml-sp-new.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -184,7 +184,7 @@ For each attribute, you can set:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Default NameID format</strong>: if no NameID format is requested, or the NameID format undefined, this NameID format will be used. If no value, the default NameID format is Email.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Force NameID session key</strong>: if empty, the NameID mapping defined in <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service</a> configuration will be used. You can force here another session key that will be used as NameID content.</div>
|
||||
<li class="level1"><div class="li"> <strong>Force NameID session key</strong>: if empty, the NameID mapping defined in <a href="../../documentation/1.9/samlservice.html" class="wikilink1" title="documentation:1.9:samlservice">SAML service</a> configuration will be used. You can force here another session key that will be used as NameID content.</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>One Time Use</strong>: set the OneTimeUse flag in authentication response (<code><Condtions></code>).</div>
|
||||
</li>
|
||||
|
|
@ -215,7 +215,7 @@ For each attribute, you can set:
|
|||
<div class="level5">
|
||||
|
||||
<p>
|
||||
These options override service signature options (see <a href="../../documentation/2.0/samlservice.html#general_options" class="wikilink1" title="documentation:2.0:samlservice">SAML service configuration</a>).
|
||||
These options override service signature options (see <a href="../../documentation/1.9/samlservice.html#general_options" class="wikilink1" title="documentation:1.9:samlservice">SAML service configuration</a>).
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Sign <abbr title="Single Sign On">SSO</abbr> message</strong>: sign <abbr title="Single Sign On">SSO</abbr> message</div>
|
||||
|
|
@ -78,13 +78,8 @@ You can add this repository to have recent packages:
|
|||
</p>
|
||||
<pre class="code">vi /etc/apt/sources.list.d/lemonldap-ng.list</pre>
|
||||
<pre class="file"># LemonLDAP::NG repository
|
||||
deb http://lemonldap-ng.org/deb squeeze main
|
||||
deb-src http://lemonldap-ng.org/deb squeeze main</pre>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">Repository is named squeeze but works for all Debian/Ubuntu versions
|
||||
</div></p>
|
||||
</p>
|
||||
deb http://lemonldap-ng.org/deb stable main
|
||||
deb-src http://lemonldap-ng.org/deb stable main</pre>
|
||||
|
||||
<p>
|
||||
Run this to update packages cache:
|
||||
|
|
@ -92,7 +87,7 @@ Run this to update packages cache:
|
|||
<pre class="code">apt-get update</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT5 SECTION "LL::NG repository" [934-1370] -->
|
||||
<!-- EDIT5 SECTION "LL::NG repository" [934-1281] -->
|
||||
<h3 class="sectionedit6" id="manual_download">Manual download</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -101,7 +96,7 @@ Packages are available on the <a href="../../download.html" class="wikilink1" ti
|
|||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT6 SECTION "Manual download" [1371-1457] -->
|
||||
<!-- EDIT6 SECTION "Manual download" [1282-1368] -->
|
||||
<h2 class="sectionedit7" id="package_gpg_signature">Package GPG signature</h2>
|
||||
<div class="level2">
|
||||
|
||||
|
|
@ -115,23 +110,23 @@ Install it to trust packages:
|
|||
<pre class="code">apt-key add rpm-gpg-key-ow2</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT7 SECTION "Package GPG signature" [1458-1626] -->
|
||||
<!-- EDIT7 SECTION "Package GPG signature" [1369-1537] -->
|
||||
<h2 class="sectionedit8" id="install_packages">Install packages</h2>
|
||||
<div class="level2">
|
||||
|
||||
</div>
|
||||
<!-- EDIT8 SECTION "Install packages" [1627-1656] -->
|
||||
<!-- EDIT8 SECTION "Install packages" [1538-1567] -->
|
||||
<h3 class="sectionedit9" id="with_aptitude">With aptitude</h3>
|
||||
<div class="level3">
|
||||
<pre class="code">aptitude install lemonldap-ng</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT9 SECTION "With aptitude" [1657-1727] -->
|
||||
<!-- EDIT9 SECTION "With aptitude" [1568-1638] -->
|
||||
<h3 class="sectionedit10" id="with_dpkg">With dpkg</h3>
|
||||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Before installing the packages, install <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">dependencies</a>.
|
||||
Before installing the packages, install <a href="../../documentation/1.9/prereq.html" class="wikilink1" title="documentation:1.9:prereq">dependencies</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -140,12 +135,12 @@ Then:
|
|||
<pre class="code">dpkg -i liblemonldap-ng-* lemonldap-ng*</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT10 SECTION "With dpkg" [1728-1876] -->
|
||||
<!-- EDIT10 SECTION "With dpkg" [1639-1787] -->
|
||||
<h2 class="sectionedit11" id="first_configuration_steps">First configuration steps</h2>
|
||||
<div class="level2">
|
||||
|
||||
</div>
|
||||
<!-- EDIT11 SECTION "First configuration steps" [1877-1915] -->
|
||||
<!-- EDIT11 SECTION "First configuration steps" [1788-1826] -->
|
||||
<h3 class="sectionedit12" id="change_default_dns_domain">Change default DNS domain</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -155,7 +150,7 @@ By default, <abbr title="Domain Name System">DNS</abbr> domain is <code>example.
|
|||
<pre class="code shell">sed -i 's/example\.com/ow2.org/g' /etc/lemonldap-ng/* /var/lib/lemonldap-ng/conf/lmConf-1 /var/lib/lemonldap-ng/test/index.pl</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT12 SECTION "Change default DNS domain" [1916-2230] -->
|
||||
<!-- EDIT12 SECTION "Change default DNS domain" [1827-2141] -->
|
||||
<h3 class="sectionedit13" id="enable_llng_sites">Enable LL::NG sites</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -179,7 +174,7 @@ Restart Apache:
|
|||
apache2ctl restart</pre>
|
||||
|
||||
</div>
|
||||
<!-- EDIT13 SECTION "Enable LL::NG sites" [2231-2583] -->
|
||||
<!-- EDIT13 SECTION "Enable LL::NG sites" [2142-2494] -->
|
||||
<h3 class="sectionedit14" id="reload_virtual_host">Reload virtual host</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -194,12 +189,12 @@ To allow the manager to reload the configuration, register the reload virtual ho
|
|||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT14 SECTION "Reload virtual host" [2584-2885] -->
|
||||
<!-- EDIT14 SECTION "Reload virtual host" [2495-2796] -->
|
||||
<h3 class="sectionedit15" id="upgrade">Upgrade</h3>
|
||||
<div class="level3">
|
||||
|
||||
<p>
|
||||
If you upgraded <abbr title="LemonLDAP::NG">LL::NG</abbr>, check all <a href="../../documentation/2.0/upgrade.html" class="wikilink1" title="documentation:2.0:upgrade">upgrade notes</a>.
|
||||
If you upgraded <abbr title="LemonLDAP::NG">LL::NG</abbr>, check all <a href="../../documentation/1.9/upgrade.html" class="wikilink1" title="documentation:1.9:upgrade">upgrade notes</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -209,12 +204,12 @@ The upgrade process will also have migrate old configuration files into <code>/e
|
|||
<span class="re1">applicationList</span><span class="sy0">=</span><span class="re2"><span class="br0">{</span> 'Menu' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'Example' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'test1' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Application Test 1', uri <span class="sy0">=</span>> 'http://test1.example.com/', description <span class="sy0">=</span>> 'A simple application displaying authenticated user', logo <span class="sy0">=</span>> 'wheels.png', display <span class="sy0">=</span>> 'auto', <span class="br0">}</span>, <span class="br0">}</span>,'test2' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Application Test 2', uri <span class="sy0">=</span>> 'http://test2.example.com/', description <span class="sy0">=</span>> 'The same simple application displaying authenticated user', logo <span class="sy0">=</span>> 'wheels.png', display <span class="sy0">=</span>> 'auto', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>,'Administration' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'manager' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'WebSSO Manager', uri <span class="sy0">=</span>> 'http://manager.example.com/', description <span class="sy0">=</span>> 'Configure LemonLDAP::NG WebSSO', logo <span class="sy0">=</span>> 'tools.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>,'sessions' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Sessions explorer', uri <span class="sy0">=</span>> 'http://manager.example.com/sessions.pl', description <span class="sy0">=</span>> 'Explore WebSSO sessions', logo <span class="sy0">=</span>> 'tools.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>,'Documentation' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'localdoc' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Local documentation', uri <span class="sy0">=</span>> 'http://manager.example.com/doc/', description <span class="sy0">=</span>> 'Documentation supplied with LemonLDAP::NG', logo <span class="sy0">=</span>> 'docs.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>,'officialwebsite' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Offical Website', uri <span class="sy0">=</span>> 'http://wiki.lemonldap.objectweb.org/xwiki/bin/view/NG/Presentation', description <span class="sy0">=</span>> 'Official LemonLDAP::NG Website', logo <span class="sy0">=</span>> 'web.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span></span></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">applications and categories</a>, and then comment or remove the <code>applicationList</code> parameter from <code>/etc/lemonldap-ng/lemonldap-ng.ini</code>.
|
||||
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">applications and categories</a>, and then comment or remove the <code>applicationList</code> parameter from <code>/etc/lemonldap-ng/lemonldap-ng.ini</code>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT15 SECTION "Upgrade" [2886-5044] -->
|
||||
<!-- EDIT15 SECTION "Upgrade" [2797-4955] -->
|
||||
<h3 class="sectionedit16" id="dns">DNS</h3>
|
||||
<div class="level3">
|
||||
|
||||
|
|
@ -234,11 +229,11 @@ For tests with <code>example.com</code>, launch the following :
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>
|
||||
Follow the <a href="../../documentation/1.9/start.html#configuration" class="wikilink1" title="documentation:1.9:start">next steps</a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<!-- EDIT16 SECTION "DNS" [5045-5317] -->
|
||||
<!-- EDIT16 SECTION "DNS" [4956-5228] -->
|
||||
<h2 class="sectionedit17" id="file_location">File location</h2>
|
||||
<div class="level2">
|
||||
<ul>
|
||||
|
|
@ -259,7 +254,7 @@ Follow the <a href="../../documentation/2.0/start.html#configuration" class="wik
|
|||
</ul>
|
||||
|
||||
</div>
|
||||
<!-- EDIT17 SECTION "File location" [5318-5854] -->
|
||||
<!-- EDIT17 SECTION "File location" [5229-5765] -->
|
||||
<h2 class="sectionedit18" id="build_your_packages">Build your packages</h2>
|
||||
<div class="level2">
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ This schema shows the dependencies between modules:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/lemonldap-ng-packages.png?id=documentation%3A2.0%3Ainstallrpm" class="media" title="documentation:lemonldap-ng-packages.png"><img src="../../../media/documentation/lemonldap-ng-packages.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/lemonldap-ng-packages.png?id=documentation%3A1.9%3Ainstallrpm" class="media" title="documentation:lemonldap-ng-packages.png"><img src="../../../media/documentation/lemonldap-ng-packages.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -108,7 +108,7 @@ Run this to update packages cache:
|
|||
|
||||
<p>
|
||||
<p><div class="notewarning">
|
||||
You must also install the EPEL repository for non-core dependencies. See <a href="../../documentation/2.0/prereq.html#yum" class="wikilink1" title="documentation:2.0:prereq">prerequisites and dependencies</a> chapter for more.
|
||||
You must also install the EPEL repository for non-core dependencies. See <a href="../../documentation/1.9/prereq.html#yum" class="wikilink1" title="documentation:1.9:prereq">prerequisites and dependencies</a> chapter for more.
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -169,7 +169,7 @@ You can also use yum on local RPMs file:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
Before installing the packages, install all <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">dependencies</a>.
|
||||
Before installing the packages, install all <a href="../../documentation/1.9/prereq.html" class="wikilink1" title="documentation:1.9:prereq">dependencies</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -274,7 +274,7 @@ To allow the manager to reload the configuration, register the reload virtual ho
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
If you upgraded <abbr title="LemonLDAP::NG">LL::NG</abbr>, check all <a href="../../documentation/2.0/upgrade.html" class="wikilink1" title="documentation:2.0:upgrade">upgrade notes</a>.
|
||||
If you upgraded <abbr title="LemonLDAP::NG">LL::NG</abbr>, check all <a href="../../documentation/1.9/upgrade.html" class="wikilink1" title="documentation:1.9:upgrade">upgrade notes</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -294,7 +294,7 @@ The upgrade process will also have migrate old configuration files into <code>/e
|
|||
<span class="re1">applicationList</span><span class="sy0">=</span><span class="re2"><span class="br0">{</span> 'Menu' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'Example' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'test1' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Application Test 1', uri <span class="sy0">=</span>> 'http://test1.example.com/', description <span class="sy0">=</span>> 'A simple application displaying authenticated user', logo <span class="sy0">=</span>> 'wheels.png', display <span class="sy0">=</span>> 'auto', <span class="br0">}</span>, <span class="br0">}</span>,'test2' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Application Test 2', uri <span class="sy0">=</span>> 'http://test2.example.com/', description <span class="sy0">=</span>> 'The same simple application displaying authenticated user', logo <span class="sy0">=</span>> 'wheels.png', display <span class="sy0">=</span>> 'auto', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>,'Administration' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'manager' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'WebSSO Manager', uri <span class="sy0">=</span>> 'http://manager.example.com/', description <span class="sy0">=</span>> 'Configure LemonLDAP::NG WebSSO', logo <span class="sy0">=</span>> 'tools.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>,'sessions' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Sessions explorer', uri <span class="sy0">=</span>> 'http://manager.example.com/sessions.pl', description <span class="sy0">=</span>> 'Explore WebSSO sessions', logo <span class="sy0">=</span>> 'tools.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>,'Documentation' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'category', 'localdoc' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Local documentation', uri <span class="sy0">=</span>> 'http://manager.example.com/doc/', description <span class="sy0">=</span>> 'Documentation supplied with LemonLDAP::NG', logo <span class="sy0">=</span>> 'docs.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>,'officialwebsite' <span class="sy0">=</span>> <span class="br0">{</span> type <span class="sy0">=</span>> 'application', options <span class="sy0">=</span>> <span class="br0">{</span> name <span class="sy0">=</span>> 'Offical Website', uri <span class="sy0">=</span>> 'http://wiki.lemonldap.objectweb.org/xwiki/bin/view/NG/Presentation', description <span class="sy0">=</span>> 'Official LemonLDAP::NG Website', logo <span class="sy0">=</span>> 'web.png', display <span class="sy0">=</span>> 'on', <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span>, <span class="br0">}</span></span></pre>
|
||||
|
||||
<p>
|
||||
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">applications and categories</a>, and then comment or remove the <code>applicationList</code> parameter from <code>/etc/lemonldap-ng/lemonldap-ng.ini</code>.
|
||||
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">applications and categories</a>, and then comment or remove the <code>applicationList</code> parameter from <code>/etc/lemonldap-ng/lemonldap-ng.ini</code>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -319,7 +319,7 @@ For tests with <code>example.com</code>, launch the following :
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>
|
||||
Follow the <a href="../../documentation/1.9/start.html#configuration" class="wikilink1" title="documentation:1.9:start">next steps</a>
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -76,7 +76,7 @@ Just run the tar command:
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
First check and install the <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">prerequisites</a>.
|
||||
First check and install the <a href="../../documentation/1.9/prereq.html" class="wikilink1" title="documentation:1.9:prereq">prerequisites</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -193,7 +193,7 @@ or:
|
|||
<pre class="code">make ubuntu-install</pre>
|
||||
|
||||
<p>
|
||||
See also <a href="../../documentation/2.0/installdeb.html" class="wikilink1" title="documentation:2.0:installdeb">Debian/Ubuntu installation documentation</a>.
|
||||
See also <a href="../../documentation/1.9/installdeb.html" class="wikilink1" title="documentation:1.9:installdeb">Debian/Ubuntu installation documentation</a>.
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -276,7 +276,7 @@ For tests with the configured domain, launch the following :
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>.
|
||||
Follow the <a href="../../documentation/1.9/start.html#configuration" class="wikilink1" title="documentation:1.9:start">next steps</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -38,7 +38,7 @@ Main differences with mod_proxy:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> The whole Location value is replaced, including the scheme (http or https), which can help to manage redirections below SSL hardware equipments</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> It is compliant with the <a href="../../documentation/2.0/formreplay.html" class="wikilink1" title="documentation:2.0:formreplay">form replay</a> feature</div>
|
||||
<li class="level1"><div class="li"> It is compliant with the <a href="../../documentation/1.9/formreplay.html" class="wikilink1" title="documentation:1.9:formreplay">form replay</a> feature</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -24,14 +24,14 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
This works like <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File backend</a>, except that data are serialized in JSON.
|
||||
This works like <a href="../../documentation/1.9/fileconfbackend.html" class="wikilink1" title="documentation:1.9:fileconfbackend">File backend</a>, except that data are serialized in JSON.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">This configuration storage can be shared between different hosts using:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP configuration backend proxy</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP configuration backend proxy</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> any files sharing system (NFS, NAS, SAN,…)</div>
|
||||
</li>
|
||||
|
|
@ -306,7 +306,7 @@ The important things to check are:
|
|||
<div class="level3">
|
||||
|
||||
<p>
|
||||
See <a href="../../documentation/2.0/authapache.html#llng" class="wikilink1" title="documentation:2.0:authapache">Apache authentication module configuration</a>.
|
||||
See <a href="../../documentation/1.9/authapache.html#llng" class="wikilink1" title="documentation:1.9:authapache">Apache authentication module configuration</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -33,7 +33,7 @@ You can choose to store LemonLDAP::NG configuration in an LDAP directory.
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/configuration-ldap.png?id=documentation%3A2.0%3Aldapconfbackend" class="media" title="documentation:configuration-ldap.png"><img src="../../../media/documentation/configuration-ldap.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/configuration-ldap.png?id=documentation%3A1.9%3Aldapconfbackend" class="media" title="documentation:configuration-ldap.png"><img src="../../../media/documentation/configuration-ldap.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -36,9 +36,9 @@
|
|||
Steps:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">Prepare the LDAP server and the LL::NG configuration file</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/ldapconfbackend.html" class="wikilink1" title="documentation:1.9:ldapconfbackend">Prepare the LDAP server and the LL::NG configuration file</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/changeconfbackend.html" class="wikilink1" title="documentation:2.0:changeconfbackend">Convert existing configuration</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/changeconfbackend.html" class="wikilink1" title="documentation:1.9:changeconfbackend">Convert existing configuration</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Restart all your Apache servers</div>
|
||||
</li>
|
||||
|
|
@ -53,7 +53,7 @@ Steps:
|
|||
Steps:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> Follow <a href="../../documentation/2.0/ldapsessionbackend.html" class="wikilink1" title="documentation:2.0:ldapsessionbackend">LDAP session backend</a> doc</div>
|
||||
<li class="level1"><div class="li"> Follow <a href="../../documentation/1.9/ldapsessionbackend.html" class="wikilink1" title="documentation:1.9:ldapsessionbackend">LDAP session backend</a> doc</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -54,11 +54,11 @@ By default, login time and <abbr title="Internet Protocol">IP</abbr> address are
|
|||
</p>
|
||||
|
||||
<p>
|
||||
To allow the Login History tab in Menu, configure it in <code>General Parameters</code> > <code>Portal</code> > <code>Menu</code> > <code>Modules</code> (see <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0:portalmenu">portal menu configuration</a>).
|
||||
To allow the Login History tab in Menu, configure it in <code>General Parameters</code> > <code>Portal</code> > <code>Menu</code> > <code>Modules</code> (see <a href="../../documentation/1.9/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.9:portalmenu">portal menu configuration</a>).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
You can also display a check box on the authentication form, to allow user to see their login history before beeing redirected to the protected application (see <a href="../../documentation/2.0/portalcustom.html#other_parameters" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>).
|
||||
You can also display a check box on the authentication form, to allow user to see their login history before beeing redirected to the protected application (see <a href="../../documentation/1.9/portalcustom.html#other_parameters" class="wikilink1" title="documentation:1.9:portalcustom">portal customization</a>).
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -29,7 +29,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Even if LL:NG can catch logout <abbr title="Uniform Resource Locator">URL</abbr> trough <a href="../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">virtual host rules</a>, you can have the need to forward a logout to other applications, to close their local sessions.
|
||||
Even if LL:NG can catch logout <abbr title="Uniform Resource Locator">URL</abbr> trough <a href="../../documentation/1.9/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.9:writingrulesand_headers">virtual host rules</a>, you can have the need to forward a logout to other applications, to close their local sessions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -84,7 +84,7 @@ But you will rather prefer to use an Apache authentication module, like for exam
|
|||
</p>
|
||||
|
||||
<p>
|
||||
By default, you will have a manager virtual host define in configuration. If not Go on Manager, and declare Manager as a new <a href="../../documentation/2.0/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:2.0:configvhost">virtual host</a>, for example <code>manager.example.com</code>. You can then set the access rule. No headers are needed.
|
||||
By default, you will have a manager virtual host define in configuration. If not Go on Manager, and declare Manager as a new <a href="../../documentation/1.9/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.9:configvhost">virtual host</a>, for example <code>manager.example.com</code>. You can then set the access rule. No headers are needed.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -125,7 +125,7 @@ Restart Apache and try to log on Manager. You should be redirected to <abbr titl
|
|||
</p>
|
||||
|
||||
<p>
|
||||
You can then add the Manager as <a href="../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">an application in the menu</a>.
|
||||
You can then add the Manager as <a href="../../documentation/1.9/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.9:portalmenu">an application in the menu</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -36,7 +36,7 @@
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
To keep Memcached performance level and <abbr title="LemonLDAP::NG">LL::NG</abbr> features, you can replace <a href="http://memcached.org/" class="urlextern" title="http://memcached.org/" rel="nofollow">Memcached</a> by <a href="http://code.google.com/p/redis/" class="urlextern" title="http://code.google.com/p/redis/" rel="nofollow">Redis</a> using <a href="../../documentation/2.0/nosqlsessionbackend.html" class="wikilink1" title="documentation:2.0:nosqlsessionbackend">NoSQL session backend</a>.
|
||||
To keep Memcached performance level and <abbr title="LemonLDAP::NG">LL::NG</abbr> features, you can replace <a href="http://memcached.org/" class="urlextern" title="http://memcached.org/" rel="nofollow">Memcached</a> by <a href="http://code.google.com/p/redis/" class="urlextern" title="http://code.google.com/p/redis/" rel="nofollow">Redis</a> using <a href="../../documentation/1.9/nosqlsessionbackend.html" class="wikilink1" title="documentation:1.9:nosqlsessionbackend">NoSQL session backend</a>.
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
<div class="level1">
|
||||
|
||||
<p>
|
||||
<a href="../../documentation/2.0/status.html" class="wikilink1" title="documentation:2.0:status">The status page</a> can be read by <a href="http://oss.oetiker.ch/mrtg/" class="urlextern" title="http://oss.oetiker.ch/mrtg/" rel="nofollow">MRTG</a> using the script <strong>lmng-mrtg</strong> that can be found in manager example directory.
|
||||
<a href="../../documentation/1.9/status.html" class="wikilink1" title="documentation:1.9:status">The status page</a> can be read by <a href="http://oss.oetiker.ch/mrtg/" class="urlextern" title="http://oss.oetiker.ch/mrtg/" rel="nofollow">MRTG</a> using the script <strong>lmng-mrtg</strong> that can be found in manager example directory.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -36,9 +36,9 @@
|
|||
Steps:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">Prepare the database and the LL::NG configuration file</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/sqlconfbackend.html" class="wikilink1" title="documentation:1.9:sqlconfbackend">Prepare the database and the LL::NG configuration file</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/changeconfbackend.html" class="wikilink1" title="documentation:2.0:changeconfbackend">Convert existing configuration</a></div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/changeconfbackend.html" class="wikilink1" title="documentation:1.9:changeconfbackend">Convert existing configuration</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Restart all your Apache servers</div>
|
||||
</li>
|
||||
|
|
@ -55,9 +55,9 @@ Steps:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> Choose one of the following:</div>
|
||||
<ul>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/browseablesessionbackend.html" class="wikilink1" title="documentation:2.0:browseablesessionbackend">Using Apache::Session::Browseable::MySQL</a> (recommended for best performances)</div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/browseablesessionbackend.html" class="wikilink1" title="documentation:1.9:browseablesessionbackend">Using Apache::Session::Browseable::MySQL</a> (recommended for best performances)</div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/sqlsessionbackend.html" class="wikilink1" title="documentation:2.0:sqlsessionbackend">Using Apache::Session::MySQL</a> <em>(if you choose this option, then read <a href="../../documentation/2.0/performances.html#apachesession_performances" class="wikilink1" title="documentation:2.0:performances">how to increase MySQL performances</a>)</em></div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/sqlsessionbackend.html" class="wikilink1" title="documentation:1.9:sqlsessionbackend">Using Apache::Session::MySQL</a> <em>(if you choose this option, then read <a href="../../documentation/1.9/performances.html#apachesession_performances" class="wikilink1" title="documentation:1.9:performances">how to increase MySQL performances</a>)</em></div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
@ -60,7 +60,7 @@ In the manager: set <a href="http://search.cpan.org/perldoc?Apache::Session::Red
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Restrict network access to the redis server. For remote servers, you can use <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a> in cunjunction to increase security for remote server that access through an unsecure network
|
||||
Restrict network access to the redis server. For remote servers, you can use <a href="../../documentation/1.9/soapsessionbackend.html" class="wikilink1" title="documentation:1.9:soapsessionbackend">SOAP session backend</a> in cunjunction to increase security for remote server that access through an unsecure network
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -74,7 +74,7 @@ You can change default parameters using the “notificationStorage” and “not
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Parameters for File backend are the same as <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File configuration backend</a>.
|
||||
Parameters for File backend are the same as <a href="../../documentation/1.9/fileconfbackend.html" class="wikilink1" title="documentation:1.9:fileconfbackend">File configuration backend</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -109,7 +109,7 @@ To summary available options:
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Parameters for <abbr title="Database Interface">DBI</abbr> backend are the same as <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">DBI configuration backend</a>.
|
||||
Parameters for <abbr title="Database Interface">DBI</abbr> backend are the same as <a href="../../documentation/1.9/sqlconfbackend.html" class="wikilink1" title="documentation:1.9:sqlconfbackend">DBI configuration backend</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -150,7 +150,7 @@ To summary available options:
|
|||
<div class="level4">
|
||||
|
||||
<p>
|
||||
Parameters for LDAP backend are the same as <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP configuration backend</a>.
|
||||
Parameters for LDAP backend are the same as <a href="../../documentation/1.9/ldapconfbackend.html" class="wikilink1" title="documentation:1.9:ldapconfbackend">LDAP configuration backend</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -288,7 +288,7 @@ In Manager, click on <code>notifications explorer</code> and then on the <code>C
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/manager/notifications_explorer_create.png?id=documentation%3A2.0%3Anotifications" class="media" title="screenshots:1.1:manager:notifications_explorer_create.png"><img src="../../../media/screenshots/1.1/manager/notifications_explorer_create.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/manager/notifications_explorer_create.png?id=documentation%3A1.9%3Anotifications" class="media" title="screenshots:1.1:manager:notifications_explorer_create.png"><img src="../../../media/screenshots/1.1/manager/notifications_explorer_create.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -392,7 +392,7 @@ You've simply to insert a notification and connect to the portal using the
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/notifications/sample_notification.png?id=documentation%3A2.0%3Anotifications" class="media" title="screenshots:1.1:notifications:sample_notification.png"><img src="../../../media/screenshots/1.1/notifications/sample_notification.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/notifications/sample_notification.png?id=documentation%3A1.9%3Anotifications" class="media" title="screenshots:1.1:notifications:sample_notification.png"><img src="../../../media/screenshots/1.1/notifications/sample_notification.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -29,7 +29,7 @@
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Be sure that mod_rewrite is installed and that OpenID Connect rewrite rules are activated in <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a>:
|
||||
Be sure that mod_rewrite is installed and that OpenID Connect rewrite rules are activated in <a href="../../documentation/1.9/configlocation.html#portal" class="wikilink1" title="documentation:1.9:configlocation">Apache portal configuration</a>:
|
||||
</p>
|
||||
<pre class="code file apache"> <span class="co1"># OpenID Connect Issuer</span>
|
||||
<<span class="kw3">IfModule</span> mod_rewrite.c>
|
||||
|
|
@ -26,7 +26,7 @@
|
|||
<p>
|
||||
<p><div class="notetip">
|
||||
Click on a column header to sort table.
|
||||
The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or in Perl scripts to override configuration parameters (see <a href="../../documentation/2.0/configlocation.html" class="wikilink1" title="documentation:2.0:configlocation">configuration location</a>).
|
||||
The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or in Perl scripts to override configuration parameters (see <a href="../../documentation/1.9/configlocation.html" class="wikilink1" title="documentation:1.9:configlocation">configuration location</a>).
|
||||
|
||||
</div></p>
|
||||
</p>
|
||||
|
|
@ -594,7 +594,7 @@ The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or
|
|||
</tr>
|
||||
</thead>
|
||||
<tr class="row1 rowodd">
|
||||
<td class="col0"> <abbr title="Database Interface">DBI</abbr> connection string </td><td class="col1"> dbiChain </td><td class="col2" rowspan="4"> <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">CDBI / RDBI</a> </td>
|
||||
<td class="col0"> <abbr title="Database Interface">DBI</abbr> connection string </td><td class="col1"> dbiChain </td><td class="col2" rowspan="4"> <a href="../../documentation/1.9/sqlconfbackend.html" class="wikilink1" title="documentation:1.9:sqlconfbackend">CDBI / RDBI</a> </td>
|
||||
</tr>
|
||||
<tr class="row2 roweven">
|
||||
<td class="col0"> <abbr title="Database Interface">DBI</abbr> user </td><td class="col1"> dbiUser </td>
|
||||
|
|
@ -606,10 +606,10 @@ The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or
|
|||
<td class="col0"> <abbr title="Database Interface">DBI</abbr> table name </td><td class="col1"> dbiTable </td>
|
||||
</tr>
|
||||
<tr class="row5 rowodd">
|
||||
<td class="col0"> Storage directory </td><td class="col1"> dirName </td><td class="col2"> <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File</a> </td>
|
||||
<td class="col0"> Storage directory </td><td class="col1"> dirName </td><td class="col2"> <a href="../../documentation/1.9/fileconfbackend.html" class="wikilink1" title="documentation:1.9:fileconfbackend">File</a> </td>
|
||||
</tr>
|
||||
<tr class="row6 roweven">
|
||||
<td class="col0"> LDAP server </td><td class="col1"> ldapServer </td><td class="col2" rowspan="7"> <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP</a> </td>
|
||||
<td class="col0"> LDAP server </td><td class="col1"> ldapServer </td><td class="col2" rowspan="7"> <a href="../../documentation/1.9/ldapconfbackend.html" class="wikilink1" title="documentation:1.9:ldapconfbackend">LDAP</a> </td>
|
||||
</tr>
|
||||
<tr class="row7 rowodd">
|
||||
<td class="col0"> LDAP port </td><td class="col1"> ldapPort </td>
|
||||
|
|
@ -630,7 +630,7 @@ The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or
|
|||
<td class="col0"> Certificate authorities directory </td><td class="col1"> caPath </td>
|
||||
</tr>
|
||||
<tr class="row13 rowodd">
|
||||
<td class="col0"> SOAP server location (<abbr title="Uniform Resource Locator">URL</abbr>) </td><td class="col1"> proxy </td><td class="col2" rowspan="2"> <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP</a> </td>
|
||||
<td class="col0"> SOAP server location (<abbr title="Uniform Resource Locator">URL</abbr>) </td><td class="col1"> proxy </td><td class="col2" rowspan="2"> <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP</a> </td>
|
||||
</tr>
|
||||
<tr class="row14 roweven">
|
||||
<td class="col0"> <a href="http://search.cpan.org/perldoc?LWP::UserAgent" class="urlextern" title="http://search.cpan.org/perldoc?LWP::UserAgent" rel="nofollow">LWP::UserAgent</a> parameters </td><td class="col1"> proxyOptions </td>
|
||||
|
|
@ -42,7 +42,7 @@ So, to keep user password in session, you cannot just export the password variab
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> As this may be a security hole, password store in session is not activated by default</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> This mechanism can only work with authentication backends using a login/password form (<a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP</a>, <a href="../../documentation/2.0/authdbi.html" class="wikilink1" title="documentation:2.0:authdbi">DBI</a>, …)</div>
|
||||
<li class="level1"><div class="li"> This mechanism can only work with authentication backends using a login/password form (<a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP</a>, <a href="../../documentation/1.9/authdbi.html" class="wikilink1" title="documentation:1.9:authdbi">DBI</a>, …)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -60,7 +60,7 @@ Handlers check rights and calculate headers for each HTTP hit. So to improve per
|
|||
Macros and groups are calculated during authentication process by the portal:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> macros are used to extend (or rewrite) <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables</a>. A macro is stored as attributes: it can contain boolean results or any string</div>
|
||||
<li class="level1"><div class="li"> macros are used to extend (or rewrite) <a href="../../documentation/1.9/exportedvars.html" class="wikilink1" title="documentation:1.9:exportedvars">exported variables</a>. A macro is stored as attributes: it can contain boolean results or any string</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> groups are stored as space-separated strings in the special attribute “groups”: it contains the names of groups whose rules were returned true for the current user</div>
|
||||
</li>
|
||||
|
|
@ -31,33 +31,33 @@ The portal is the main component of <abbr title="LemonLDAP::NG">LL::NG</abbr>. I
|
|||
<ul>
|
||||
<li class="level2"><div class="li"> Web based for normal users:</div>
|
||||
<ul>
|
||||
<li class="level3"><div class="li"> using own database (<a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP</a>, <a href="../../documentation/2.0/authdbi.html" class="wikilink1" title="documentation:2.0:authdbi">SQL</a>, …)</div>
|
||||
<li class="level3"><div class="li"> using own database (<a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP</a>, <a href="../../documentation/1.9/authdbi.html" class="wikilink1" title="documentation:1.9:authdbi">SQL</a>, …)</div>
|
||||
</li>
|
||||
<li class="level3"><div class="li"> using Apache authentication system (used for <a href="../../documentation/2.0/authssl.html" class="wikilink1" title="documentation:2.0:authssl">SSL</a>, <a href="../../documentation/2.0/authapache.html" class="wikilink1" title="documentation:2.0:authapache">Kerberos</a>, <a href="../../documentation/2.0/authapache.html" class="wikilink1" title="documentation:2.0:authapache">HTTP basic authentication</a>, …)</div>
|
||||
<li class="level3"><div class="li"> using Apache authentication system (used for <a href="../../documentation/1.9/authssl.html" class="wikilink1" title="documentation:1.9:authssl">SSL</a>, <a href="../../documentation/1.9/authapache.html" class="wikilink1" title="documentation:1.9:authapache">Kerberos</a>, <a href="../../documentation/1.9/authapache.html" class="wikilink1" title="documentation:1.9:authapache">HTTP basic authentication</a>, …)</div>
|
||||
</li>
|
||||
<li class="level3"><div class="li"> using external identity provider (<a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML</a>, <a href="../../documentation/2.0/authopenid.html" class="wikilink1" title="documentation:2.0:authopenid">OpenID</a>, <a href="../../documentation/2.0/authcas.html" class="wikilink1" title="documentation:2.0:authcas">CAS</a>, <a href="../../documentation/2.0/authtwitter.html" class="wikilink1" title="documentation:2.0:authtwitter">Twitter</a>, other <abbr title="LemonLDAP::NG">LL::NG</abbr> system, …)</div>
|
||||
<li class="level3"><div class="li"> using external identity provider (<a href="../../documentation/1.9/authsaml.html" class="wikilink1" title="documentation:1.9:authsaml">SAML</a>, <a href="../../documentation/1.9/authopenid.html" class="wikilink1" title="documentation:1.9:authopenid">OpenID</a>, <a href="../../documentation/1.9/authcas.html" class="wikilink1" title="documentation:1.9:authcas">CAS</a>, <a href="../../documentation/1.9/authtwitter.html" class="wikilink1" title="documentation:1.9:authtwitter">Twitter</a>, other <abbr title="LemonLDAP::NG">LL::NG</abbr> system, …)</div>
|
||||
</li>
|
||||
<li class="level3"><div class="li"> all together (based on user <a href="../../documentation/2.0/authchoice.html" class="wikilink1" title="documentation:2.0:authchoice">choice</a>, <a href="../../documentation/2.0/authmulti.html" class="wikilink1" title="documentation:2.0:authmulti">rules</a>, …)</div>
|
||||
<li class="level3"><div class="li"> all together (based on user <a href="../../documentation/1.9/authchoice.html" class="wikilink1" title="documentation:1.9:authchoice">choice</a>, <a href="../../documentation/1.9/authmulti.html" class="wikilink1" title="documentation:1.9:authmulti">rules</a>, …)</div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/soapservices.html" class="wikilink1" title="documentation:2.0:soapservices">SOAP based</a> for client-server software, specific development, …</div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/soapservices.html" class="wikilink1" title="documentation:1.9:soapservices">SOAP based</a> for client-server software, specific development, …</div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Identity provider</strong>: <abbr title="LemonLDAP::NG">LL::NG</abbr> is able to provide identity service using:</div>
|
||||
<ul>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML</a></div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/idpsaml.html" class="wikilink1" title="documentation:1.9:idpsaml">SAML</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpopenid.html" class="wikilink1" title="documentation:2.0:idpopenid">OpenID</a></div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/idpopenid.html" class="wikilink1" title="documentation:1.9:idpopenid">OpenID</a></div>
|
||||
</li>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS</a></div>
|
||||
<li class="level2"><div class="li"> <a href="../../documentation/1.9/idpcas.html" class="wikilink1" title="documentation:1.9:idpcas">CAS</a></div>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/2.0/federationproxy.html" class="wikilink1" title="documentation:2.0:federationproxy">Identity provider proxy</a></strong>: <abbr title="LemonLDAP::NG">LL::NG</abbr> can be used as proxy translator between systems talking <abbr title="Security Assertion Markup Language">SAML</abbr>, OpenID, <abbr title="Central Authentication Service">CAS</abbr>, …</div>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.9/federationproxy.html" class="wikilink1" title="documentation:1.9:federationproxy">Identity provider proxy</a></strong>: <abbr title="LemonLDAP::NG">LL::NG</abbr> can be used as proxy translator between systems talking <abbr title="Security Assertion Markup Language">SAML</abbr>, OpenID, <abbr title="Central Authentication Service">CAS</abbr>, …</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Internal SOAP server</strong> used by <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP configuration backend</a> and usable for specific development (see <a href="../../documentation/2.0/soapservices.html" class="wikilink1" title="documentation:2.0:soapservices">SOAP services</a> for more)</div>
|
||||
<li class="level1"><div class="li"> <strong>Internal SOAP server</strong> used by <a href="../../documentation/1.9/soapconfbackend.html" class="wikilink1" title="documentation:1.9:soapconfbackend">SOAP configuration backend</a> and usable for specific development (see <a href="../../documentation/1.9/soapservices.html" class="wikilink1" title="documentation:1.9:soapservices">SOAP services</a> for more)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Interactive <strong>management of user passwords</strong>:</div>
|
||||
<ul>
|
||||
|
|
@ -69,9 +69,9 @@ The portal is the main component of <abbr title="LemonLDAP::NG">LL::NG</abbr>. I
|
|||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/2.0/portalmenu.html" class="wikilink1" title="documentation:2.0:portalmenu">Application menu</a></strong>: display authorized applications in categories</div>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.9/portalmenu.html" class="wikilink1" title="documentation:1.9:portalmenu">Application menu</a></strong>: display authorized applications in categories</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/2.0/notifications.html" class="wikilink1" title="documentation:2.0:notifications">Notifications</a></strong>: prompt users with a message if found in the notification database</div>
|
||||
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.9/notifications.html" class="wikilink1" title="documentation:1.9:notifications">Notifications</a></strong>: prompt users with a message if found in the notification database</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -84,13 +84,13 @@ The portal is the main component of <abbr title="LemonLDAP::NG">LL::NG</abbr>. I
|
|||
<abbr title="LemonLDAP::NG">LL::NG</abbr> portal is a modular component. It needs 4 modules to work:
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:2.0:start">Authentication</a>: how check user credentials</div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.9:start">Authentication</a>: how check user credentials</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:2.0:start">User database</a>: where collect user information</div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.9:start">User database</a>: where collect user information</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:2.0:start">Password database</a>: where change password</div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.9:start">Password database</a>: where change password</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/2.0/start.html#identity_provider" class="wikilink1" title="documentation:2.0:start">Identity provider</a>: how forward user identity</div>
|
||||
<li class="level1"><div class="li"> <a href="../../documentation/1.9/start.html#identity_provider" class="wikilink1" title="documentation:1.9:start">Identity provider</a>: how forward user identity</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -116,7 +116,7 @@ The portal is the main component of <abbr title="LemonLDAP::NG">LL::NG</abbr>. I
|
|||
</li>
|
||||
<li class="level1"><div class="li"> Provides identity if asked</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Build <a href="../../documentation/2.0/ssocookie.html" class="wikilink1" title="documentation:2.0:ssocookie">cookie(s)</a></div>
|
||||
<li class="level1"><div class="li"> Build <a href="../../documentation/1.9/ssocookie.html" class="wikilink1" title="documentation:1.9:ssocookie">cookie(s)</a></div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> Redirect user to the asked <abbr title="Uniform Resource Locator">URL</abbr> or display menu</div>
|
||||
</li>
|
||||
|
|
@ -66,7 +66,7 @@ You can change the default skin in Manager: <code>General Parameters</code> >
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-2-portalskin.png?id=documentation%3A2.0%3Aportalcustom" class="media" title="documentation:manager-2-portalskin.png"><img src="../../../media/documentation/manager-2-portalskin.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/manager-2-portalskin.png?id=documentation%3A1.9%3Aportalcustom" class="media" title="documentation:manager-2-portalskin.png"><img src="../../../media/documentation/manager-2-portalskin.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -220,9 +220,9 @@ This node allows to enable/disable buttons on the login page:
|
|||
<ul>
|
||||
<li class="level1"><div class="li"> <strong>Check last logins</strong>: displays a checkbox on login form, allowing user to check his login history right after opening session</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Reset password</strong>: display a link to <a href="../../documentation/2.0/resetpassword.html" class="wikilink1" title="documentation:2.0:resetpassword">reset your password page</a> (for password based authentication backends)</div>
|
||||
<li class="level1"><div class="li"> <strong>Reset password</strong>: display a link to <a href="../../documentation/1.9/resetpassword.html" class="wikilink1" title="documentation:1.9:resetpassword">reset your password page</a> (for password based authentication backends)</div>
|
||||
</li>
|
||||
<li class="level1"><div class="li"> <strong>Register</strong>: display a link to <a href="../../documentation/2.0/register.html" class="wikilink1" title="documentation:2.0:register">register page</a> (for password based authentication backends)</div>
|
||||
<li class="level1"><div class="li"> <strong>Register</strong>: display a link to <a href="../../documentation/1.9/register.html" class="wikilink1" title="documentation:1.9:register">register page</a> (for password based authentication backends)</div>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ You can use <code>0</code> or <code>1</code> to disable/enable the module, or us
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
<a href="../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0: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>).
|
||||
<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>
|
||||
|
|
@ -84,7 +84,7 @@ Application parameters:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-menu-application.png?id=documentation%3A2.0%3Aportalmenu" class="media" title="documentation:manager-menu-application.png"><img src="../../../media/documentation/manager-menu-application.png" class="mediacenter" alt="" /></a>
|
||||
<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>
|
||||
|
|
@ -115,7 +115,7 @@ Application parameters:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/manager-menu-application-logo.png?id=documentation%3A2.0%3Aportalmenu" class="media" title="documentation:manager-menu-application-logo.png"><img src="../../../media/documentation/manager-menu-application-logo.png" class="mediacenter" alt="" /></a>
|
||||
<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>
|
||||
|
|
@ -33,7 +33,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
LemonLDAP::NG allows to use this model. You should use an <a href="../../documentation/2.0/authldap.html#schema_extension" class="wikilink1" title="documentation:2.0:authldap">extended LDAP schema</a> (or any users database extension), but this can works with standard attributes.
|
||||
LemonLDAP::NG allows to use this model. You should use an <a href="../../documentation/1.9/authldap.html#schema_extension" class="wikilink1" title="documentation:1.9:authldap">extended LDAP schema</a> (or any users database extension), but this can works with standard attributes.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -72,7 +72,7 @@ Now imagine the following DIT:
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/documentation/dia_dit_roles.png?id=documentation%3A2.0%3Arbac" class="media" title="documentation:dia_dit_roles.png"><img src="../../../media/documentation/dia_dit_roles.png" class="mediacenter" alt="" /></a>
|
||||
<a href="/_detail/documentation/dia_dit_roles.png?id=documentation%3A1.9%3Arbac" class="media" title="documentation:dia_dit_roles.png"><img src="../../../media/documentation/dia_dit_roles.png" class="mediacenter" alt="" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -48,7 +48,7 @@ These parameters can be configured in Manager, in <code>General Parameters</code
|
|||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">These settings can be overriden per virtual host, see <a href="../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">virtual host management</a>.
|
||||
<p><div class="notetip">These settings can be overriden per virtual host, see <a href="../../documentation/1.9/configvhost.html" class="wikilink1" title="documentation:1.9:configvhost">virtual host management</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ This feature is a page that allows a user to create an account. The steps are th
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
You can enable the “Create your account” button in <a href="../../documentation/2.0/portalcustom.html" class="wikilink1" title="documentation:2.0:portalcustom">portal customization parameters</a>.
|
||||
You can enable the “Create your account” button in <a href="../../documentation/1.9/portalcustom.html" class="wikilink1" title="documentation:1.9:portalcustom">portal customization parameters</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -41,7 +41,7 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step1.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step1.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step1.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step1.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step1.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step1.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> User enters his email (or another information) in the password reset form</div>
|
||||
|
|
@ -51,7 +51,7 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step2.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step2.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> A mail with a token is sent to user</div>
|
||||
|
|
@ -59,7 +59,7 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step3.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step3.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step3.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step3.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step3.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step3.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> The user click on the link in the mail</div>
|
||||
|
|
@ -67,7 +67,7 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step4.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step4.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step4.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step4.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step4.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step4.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> <abbr title="LemonLDAP::NG">LL::NG</abbr> validate the token and propose a password change form</div>
|
||||
|
|
@ -77,7 +77,7 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step2.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step2.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step2.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
<ul>
|
||||
<li class="level1"><div class="li"> The new password is sent to user</div>
|
||||
|
|
@ -85,11 +85,11 @@ Kinematics:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step5.png?id=documentation%3A2.0%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step5.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step5.png" class="mediacenter" alt="" width="600" /></a>
|
||||
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step5.png?id=documentation%3A1.9%3Aresetpassword" class="media" title="screenshots:1.1:mailreset:mailreset_step5.png"><img src="../../../media/screenshots/1.1/mailreset/mailreset_step5.png" class="mediacenter" alt="" width="600" /></a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<p><div class="notetip">If <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP backend</a> is used, and LDAP password policy is enabled, the 'password reset flag is set to true when password is generated, so that the user is forced to change his password on next connection. This feature can be disabled in <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP configuration</a>.
|
||||
<p><div class="notetip">If <a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP backend</a> is used, and LDAP password policy is enabled, the 'password reset flag is set to true when password is generated, so that the user is forced to change his password on next connection. This feature can be disabled in <a href="../../documentation/1.9/authldap.html" class="wikilink1" title="documentation:1.9:authldap">LDAP configuration</a>.
|
||||
</div></p>
|
||||
</p>
|
||||
|
||||
|
|
@ -104,7 +104,7 @@ Kinematics:
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
The reset password link must be activated, see <a href="../../documentation/2.0/portalcustom.html#other_parameters" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>.
|
||||
The reset password link must be activated, see <a href="../../documentation/1.9/portalcustom.html#other_parameters" class="wikilink1" title="documentation:1.9:portalcustom">portal customization</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -66,7 +66,7 @@ More information about Safe on <a href="http://search.cpan.org/search?query=Safe
|
|||
<div class="level2">
|
||||
|
||||
<p>
|
||||
Safe can be very annoying when we use <a href="../../documentation/2.0/extendedfunctions.html" class="wikilink1" title="documentation:2.0:extendedfunctions">extended functions</a> or <a href="../../documentation/2.0/customfunctions.html" class="wikilink1" title="documentation:2.0:customfunctions">custom functions</a>. In this case, you might want to disabling it.
|
||||
Safe can be very annoying when we use <a href="../../documentation/1.9/extendedfunctions.html" class="wikilink1" title="documentation:1.9:extendedfunctions">extended functions</a> or <a href="../../documentation/1.9/customfunctions.html" class="wikilink1" title="documentation:1.9:customfunctions">custom functions</a>. In this case, you might want to disabling it.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user