Update documentation in trunk, use 2.0

environments/ppa-mbqj77/deployments/1
Clément Oudot 10 years ago
parent 8332785cde
commit 247725e6d8
  1. 8
      doc/pages/contact.html
  2. 13
      doc/pages/documentation.html
  3. 206
      doc/pages/documentation/1.4/upgrade.html
  4. 4
      doc/pages/documentation/2.0/activedirectoryminihowto.html
  5. 20
      doc/pages/documentation/2.0/applications.html
  6. 8
      doc/pages/documentation/2.0/applications/authbasic.html
  7. 10
      doc/pages/documentation/2.0/applications/bugzilla.html
  8. 8
      doc/pages/documentation/2.0/applications/cornerstone.html
  9. 0
      doc/pages/documentation/2.0/applications/django.html
  10. 12
      doc/pages/documentation/2.0/applications/dokuwiki.html
  11. 12
      doc/pages/documentation/2.0/applications/drupal.html
  12. 22
      doc/pages/documentation/2.0/applications/googleapps.html
  13. 26
      doc/pages/documentation/2.0/applications/liferay.html
  14. 8
      doc/pages/documentation/2.0/applications/limesurvey.html
  15. 12
      doc/pages/documentation/2.0/applications/mediawiki.html
  16. 0
      doc/pages/documentation/2.0/applications/nginx.html
  17. 8
      doc/pages/documentation/2.0/applications/obm.html
  18. 10
      doc/pages/documentation/2.0/applications/phpldapadmin.html
  19. 2
      doc/pages/documentation/2.0/applications/roundcube.html
  20. 16
      doc/pages/documentation/2.0/applications/salesforce.html
  21. 2
      doc/pages/documentation/2.0/applications/spring.html
  22. 14
      doc/pages/documentation/2.0/applications/sympa.html
  23. 4
      doc/pages/documentation/2.0/applications/tomcat.html
  24. 12
      doc/pages/documentation/2.0/applications/zimbra.html
  25. 4
      doc/pages/documentation/2.0/authad.html
  26. 2
      doc/pages/documentation/2.0/authapache.html
  27. 2
      doc/pages/documentation/2.0/authbrowserid.html
  28. 6
      doc/pages/documentation/2.0/authcas.html
  29. 4
      doc/pages/documentation/2.0/authchoice.html
  30. 4
      doc/pages/documentation/2.0/authdbi.html
  31. 2
      doc/pages/documentation/2.0/authdemo.html
  32. 2
      doc/pages/documentation/2.0/authfacebook.html
  33. 2
      doc/pages/documentation/2.0/authgoogle.html
  34. 16
      doc/pages/documentation/2.0/authldap.html
  35. 6
      doc/pages/documentation/2.0/authmulti.html
  36. 0
      doc/pages/documentation/2.0/authnull.html
  37. 6
      doc/pages/documentation/2.0/authopenid.html
  38. 4
      doc/pages/documentation/2.0/authproxy.html
  39. 0
      doc/pages/documentation/2.0/authradius.html
  40. 12
      doc/pages/documentation/2.0/authremote.html
  41. 18
      doc/pages/documentation/2.0/authsaml.html
  42. 2
      doc/pages/documentation/2.0/authslave.html
  43. 4
      doc/pages/documentation/2.0/authssl.html
  44. 0
      doc/pages/documentation/2.0/authtwitter.html
  45. 2
      doc/pages/documentation/2.0/authwebid.html
  46. 0
      doc/pages/documentation/2.0/authyubikey.html
  47. 4
      doc/pages/documentation/2.0/browseablesessionbackend.html
  48. 2
      doc/pages/documentation/2.0/captcha.html
  49. 0
      doc/pages/documentation/2.0/cda.html
  50. 8
      doc/pages/documentation/2.0/changeconfbackend.html
  51. 14
      doc/pages/documentation/2.0/configlocation.html
  52. 10
      doc/pages/documentation/2.0/configvhost.html
  53. 4
      doc/pages/documentation/2.0/customfunctions.html
  54. 2
      doc/pages/documentation/2.0/error.html
  55. 10
      doc/pages/documentation/2.0/exportedvars.html
  56. 36
      doc/pages/documentation/2.0/extendedfunctions.html
  57. 0
      doc/pages/documentation/2.0/fastcgi.html
  58. 10
      doc/pages/documentation/2.0/federationproxy.html
  59. 2
      doc/pages/documentation/2.0/fileconfbackend.html
  60. 2
      doc/pages/documentation/2.0/filesessionbackend.html
  61. 8
      doc/pages/documentation/2.0/formreplay.html
  62. 4
      doc/pages/documentation/2.0/handlerauthbasic.html
  63. 2
      doc/pages/documentation/2.0/header_remote_user_conversion.html
  64. 4
      doc/pages/documentation/2.0/highavailability.html
  65. 8
      doc/pages/documentation/2.0/idpcas.html
  66. 16
      doc/pages/documentation/2.0/idpopenid.html
  67. 18
      doc/pages/documentation/2.0/idpsaml.html
  68. 8
      doc/pages/documentation/2.0/installdeb.html
  69. 12
      doc/pages/documentation/2.0/installrpm.html
  70. 6
      doc/pages/documentation/2.0/installtarball.html
  71. 2
      doc/pages/documentation/2.0/internalproxy.html
  72. 4
      doc/pages/documentation/2.0/jsonfileconfbackend.html
  73. 2
      doc/pages/documentation/2.0/ldapconfbackend.html
  74. 6
      doc/pages/documentation/2.0/ldapminihowto.html
  75. 0
      doc/pages/documentation/2.0/ldapsessionbackend.html
  76. 4
      doc/pages/documentation/2.0/loginhistory.html
  77. 2
      doc/pages/documentation/2.0/logoutforward.html
  78. 0
      doc/pages/documentation/2.0/logs.html
  79. 4
      doc/pages/documentation/2.0/managerprotection.html
  80. 2
      doc/pages/documentation/2.0/memcachedsessionbackend.html
  81. 2
      doc/pages/documentation/2.0/mrtg.html
  82. 8
      doc/pages/documentation/2.0/mysqlminihowto.html
  83. 2
      doc/pages/documentation/2.0/nosqlsessionbackend.html
  84. 10
      doc/pages/documentation/2.0/notifications.html
  85. 10
      doc/pages/documentation/2.0/parameterlist.html
  86. 2
      doc/pages/documentation/2.0/passwordstore.html
  87. 2
      doc/pages/documentation/2.0/performances.html
  88. 34
      doc/pages/documentation/2.0/portal.html
  89. 6
      doc/pages/documentation/2.0/portalcustom.html
  90. 6
      doc/pages/documentation/2.0/portalmenu.html
  91. 0
      doc/pages/documentation/2.0/prereq.html
  92. 4
      doc/pages/documentation/2.0/rbac.html
  93. 2
      doc/pages/documentation/2.0/redirections.html
  94. 2
      doc/pages/documentation/2.0/register.html
  95. 16
      doc/pages/documentation/2.0/resetpassword.html
  96. 2
      doc/pages/documentation/2.0/safejail.html
  97. 88
      doc/pages/documentation/2.0/samlservice.html
  98. 2
      doc/pages/documentation/2.0/securetoken.html
  99. 14
      doc/pages/documentation/2.0/security.html
  100. 6
      doc/pages/documentation/2.0/selfmadeapplication.html
  101. Some files were not shown because too many files have changed in this diff Show More

@ -146,14 +146,12 @@ We use <a href="http://jira.ow2.org" class="urlextern" title="http://jira.ow2.or
</li>
<li class="level1"><div class="li"> <strong>François-Xavier DELTOMBE</strong>: developer, tester</div>
</li>
<li class="level1"><div class="li"> <strong>Sandro CAZZANIGA</strong>: developer, tester</div>
</li>
<li class="level1"><div class="li"> <strong>David COUTADEUR</strong>: developer, tester</div>
</li>
</ul>
</div>
<!-- SECTION "Core team" [2495-2994] -->
<!-- SECTION "Core team" [2495-2950] -->
<h2><a name="past_and_present_contributors" id="past_and_present_contributors">Past and present contributors</a></h2>
<div class="level2">
@ -179,6 +177,8 @@ By alphabetical order:
</li>
<li class="level1"><div class="li"> Jean-Thomas CHECCO</div>
</li>
<li class="level1"><div class="li"> Sandro CAZZANIGA</div>
</li>
<li class="level1"><div class="li"> Thomas CHEMINEAU</div>
</li>
<li class="level1"><div class="li"> Sebastien DIAZ</div>
@ -200,4 +200,4 @@ By alphabetical order:
</ul>
</div>
<!-- SECTION "Past and present contributors" [2995-] --></div><!-- closes <div class="dokuwiki export">-->
<!-- SECTION "Past and present contributors" [2951-] --></div><!-- closes <div class="dokuwiki export">-->

@ -59,13 +59,8 @@
</div></p>
</p>
</li>
</ul>
</li>
</ul>
</div>
<!-- SECTION "Installation and configuration" [325-905] -->
<!-- SECTION "Installation and configuration" [325-946] -->
<h2><a name="development" id="development">Development</a></h2>
<div class="level2">
@ -102,7 +97,7 @@
</ul>
</div>
<!-- SECTION "Development" [906-1830] -->
<!-- SECTION "Development" [947-1871] -->
<h3><a name="translators" id="translators">Translators</a></h3>
<div class="level3">
@ -112,7 +107,7 @@ See <a href="translations.html" class="wikilink1" title="translations">translati
</p>
</div>
<!-- SECTION "Translators" [1831-1876] -->
<!-- SECTION "Translators" [1872-1917] -->
<h2><a name="other" id="other">Other</a></h2>
<div class="level2">
@ -133,4 +128,4 @@ See <a href="translations.html" class="wikilink1" title="translations">translati
</ul>
</div>
<!-- SECTION "Other" [1877-] --></div><!-- closes <div class="dokuwiki export">-->
<!-- SECTION "Other" [1918-] --></div><!-- closes <div class="dokuwiki export">-->

@ -1,206 +0,0 @@
<!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><a name="upgrade_from_13_to_14" id="upgrade_from_13_to_14">Upgrade from 1.3 to 1.4</a></h1>
<div class="level1">
<p>
<p><div class="noteclassic">If you are using packages, they should have done the upgrade process for you, but you can check here that all is in order.
</div></p>
</p>
<p>
<p><div class="noteimportant">
If you upgrade from older versions, please follow first:
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.0/upgrade.html" class="wikilink1" title="documentation:1.0:upgrade">Upgrade to 1.0</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.1/upgrade.html" class="wikilink1" title="documentation:1.1:upgrade">Upgrade to 1.1</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.2/upgrade.html" class="wikilink1" title="documentation:1.2:upgrade">Upgrade to 1.2</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.3/upgrade.html" class="wikilink1" title="documentation:1.3:upgrade">Upgrade to 1.3</a></div>
</li>
</ul>
<p>
</div></p>
</p>
</div>
<!-- SECTION "Upgrade from 1.3 to 1.4" [1-459] -->
<h2><a name="handler" id="handler">Handler</a></h2>
<div class="level2">
<p>
Handler module has been completely rewritten. You should now call the default module in your virtual host:
</p>
<pre class="code file apache">PerlHeaderParserHandler Lemonldap::NG::Handler</pre>
<p>
The main Apache handler configuration file has also been modified, check it:
</p>
<pre class="code file apache"><span class="co1"># Load LemonLDAP::NG Handler</span>
PerlOptions +GlobalRequest
PerlRequire Lemonldap/NG/Handler.pm
&nbsp;
<span class="co1"># Common error page and security parameters</span>
<span class="kw1">ErrorDocument</span> 403 http://auth.example.com/?lmError=403
<span class="kw1">ErrorDocument</span> 500 http://auth.example.com/?lmError=500
<span class="kw1">ErrorDocument</span> 503 http://auth.example.com/?lmError=503
&nbsp;
&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> reload.example.com
&nbsp;
<span class="co1"># Configuration reload mechanism (only 1 per physical server is</span>
<span class="co1"># needed): choose your URL to avoid restarting Apache when</span>
<span class="co1"># configuration change</span>
&lt;<span class="kw3">Location</span> /reload&gt;
<span class="kw1">Order</span> <span class="kw1">deny</span>,<span class="kw1">allow</span>
<span class="kw1">Deny</span> from <span class="kw2">all</span>
<span class="kw1">Allow</span> from 127.0.0.0/8
PerlHeaderParserHandler Lemonldap::NG::Handler-&gt;refresh
&lt;/<span class="kw3">Location</span>&gt;
&nbsp;
<span class="co1"># Uncomment this to activate status module</span>
<span class="co1">#&lt;Location /status&gt;</span>
<span class="co1"># Order deny,allow</span>
<span class="co1"># Deny from all</span>
<span class="co1"># Allow from 127.0.0.0/8</span>
<span class="co1"># PerlHeaderParserHandler Lemonldap::NG::Handler-&gt;status</span>
<span class="co1">#&lt;/Location&gt;</span>
&nbsp;
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
</div>
<!-- SECTION "Handler" [460-1703] -->
<h2><a name="new_portal_skin" id="new_portal_skin">New portal skin</a></h2>
<div class="level2">
<p>
We provide a new skin: bootstrap. This skin uses Twitter Bootstrap framework, and allows to have a good rendering on mobile devices. Try it!
</p>
</div>
<!-- SECTION "New portal skin" [1704-1875] -->
<h2><a name="specific_handlers" id="specific_handlers">Specific handlers</a></h2>
<div class="level2">
<p>
If you are using one of these specific handlers:
</p>
<ul>
<li class="level1"><div class="li"> AuthBasic.pm</div>
</li>
<li class="level1"><div class="li"> SecureToken.pm</div>
</li>
<li class="level1"><div class="li"> SympaAutoLogin.pm</div>
</li>
<li class="level1"><div class="li"> UpdateCookie.pm</div>
</li>
<li class="level1"><div class="li"> ZimbraPreAuth.pm</div>
</li>
</ul>
<p>
You should now change their path in you virtual host:
For example for sympa, from:
</p>
<pre class="code">
PerlRequire /usr/local/lemonldap-ng/handler/MyHandlerSympa.pm
PerlHeaderParserHandler My::Sympa
</pre>
<p>
to:
</p>
<pre class="code">
PerlRequire Lemonldap/NG/Handler/Specific/SympaAutoLogin.pm
PerlHeaderParserHandler Lemonldap::NG::Handler::Specific::SympaAutoLogin
</pre>
<p>
<p><div class="notewarning">Take care to save every specificity in these files before you do the upgrade.
</p>
<ul>
<li class="level1"><div class="li"> MyHandlerAuthBasic.pm</div>
</li>
<li class="level1"><div class="li"> MyHandler.pm</div>
</li>
<li class="level1"><div class="li"> MyHandlerSecureToken.pm</div>
</li>
<li class="level1"><div class="li"> MyHandlerSympa.pm</div>
</li>
<li class="level1"><div class="li"> MyHandlerZimbra.pm</div>
</li>
<li class="level1"><div class="li"> MyUpdateCookieHandler.pm</div>
</li>
</ul>
<p>
</div></p>
</p>
</div>
<!-- SECTION "Specific handlers" [1876-2649] -->
<h2><a name="security" id="security">Security</a></h2>
<div class="level2">
<p>
We found that the default session identifier generation may be too simple and can allow to do brute force attack to find a valid session identifier (see <a href="https://jira.ow2.org/browse/LEMONLDAP-695" class="urlextern" title="https://jira.ow2.org/browse/LEMONLDAP-695" rel="nofollow">https://jira.ow2.org/browse/LEMONLDAP-695</a>).
</p>
<p>
We recommend that you use a new generate module. Add <code>generateModule</code> key inside your sessions backend options and use <code>Lemonldap::NG::Common::Apache::Session::Generate::SHA256</code> as value.
</p>
</div>
<!-- SECTION "Security" [2650-3062] -->
<h2><a name="captcha" id="captcha">Captcha</a></h2>
<div class="level2">
<p>
Captcha now use an Apache::Session module as backend, you need to adapt your previous configuration to replace <code>captcha_data</code> and <code>captcha_output</code> by <code>captchaStorage</code> and <code>captchaStorageOptions</code>.
</p>
<p>
This allows to use a DB or <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> to share captchas in a cluster.
</p>
</div>
<!-- SECTION "Captcha" [3063-] --></div><!-- closes <div class="dokuwiki export">-->

@ -37,7 +37,7 @@ To use Active Directory as <acronym title="Lightweight Directory Access Protocol
<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/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables</a></div>
<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>
<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>
@ -50,7 +50,7 @@ To use Active Directory as <acronym title="Lightweight Directory Access Protocol
<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/1.4/authapache.html" class="wikilink1" title="documentation:1.4: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/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>
</ul>

@ -49,7 +49,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> OBM </th><th class="col1 centeralign"> Sympa </th><th class="col2 centeralign"> Zimbra </th><th class="col3 centeralign"> RoundCube </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/obm.html" class="media" title="documentation:1.4:applications:obm"><img src="../../../media/applications/obm_logo.png" class="media" alt="" /></a> </td><td class="col1 leftalign"> <a href="../../documentation/1.4/applications/sympa.html" class="media" title="documentation:1.4:applications:sympa"><img src="../../../media/applications/sympa_logo.png" class="media" alt="" /></a> </td><td class="col2 rightalign"> <a href="../../documentation/1.4/applications/zimbra.html" class="media" title="documentation:1.4:applications:zimbra"><img src="../../../media/applications/zimbra_logo.png" class="media" alt="" /></a> </td><td class="col3 rightalign"> <a href="../../documentation/1.4/applications/roundcube.html" class="media" title="documentation:1.4:applications:roundcube"><img src="../../../media/applications/roundcube_logo.png" class="media" alt="" /></a> </td>
<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>
</tr>
</table>
@ -62,7 +62,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> Dokuwiki </th><th class="col1 centeralign"> Mediawiki </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 leftalign"> <a href="../../documentation/1.4/applications/dokuwiki.html" class="media" title="documentation:1.4:applications:dokuwiki"><img src="../../../media/applications/dokuwiki_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.4/applications/mediawiki.html" class="media" title="documentation:1.4:applications:mediawiki"><img src="../../../media/applications/mediawiki_logo.png" class="media" alt="" /></a> </td>
<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>
</tr>
</table>
@ -75,7 +75,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> Drupal </th><th class="col1 centeralign"> Liferay </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/drupal.html" class="media" title="documentation:1.4:applications:drupal"><img src="../../../media/applications/drupal_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.4/applications/liferay.html" class="media" title="documentation:1.4:applications:liferay"><img src="../../../media/applications/liferay_logo.png" class="media" alt="" /></a> </td>
<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>
</tr>
</table>
@ -88,7 +88,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> Bugzilla </th><th class="col1 leftalign"> GLPI </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/bugzilla.html" class="media" title="documentation:1.4: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/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>
</tr>
</table>
@ -101,13 +101,13 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> GRR </th><th class="col1 leftalign"> phpLDAPadmin </th><th class="col2 centeralign"> LinShare </th><th class="col3 centeralign"> SAP </th>
</tr>
<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/1.4/applications/phpldapadmin.html" class="media" title="documentation:1.4: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/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>
</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/1.4/applications/limesurvey.html" class="media" title="documentation:1.4: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/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>
</tr>
</table>
@ -120,7 +120,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> Java (Spring) </th><th class="col1 centeralign"> Python (Django) </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/spring.html" class="media" title="documentation:1.4:applications:spring"><img src="../../../media/applications/spring_logo.png" class="media" alt="" /></a> </td><td class="col1 centeralign"> <a href="../../documentation/1.4/applications/django.html" class="media" title="documentation:1.4:applications:django"><img src="../../../media/applications/django_logo.png" class="media" alt="" /></a> </td>
<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>
</tr>
</table>
@ -133,7 +133,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<th class="col0 centeralign"> <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Auth-Basic </th><th class="col1 centeralign"> Tomcat </th><th class="col2 centeralign"> Nginx </th>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/authbasic.html" class="media" title="documentation:1.4:applications:authbasic"><img src="../../../media/applications/http_logo.png" class="media" alt="" /></a> </td><td class="col1 rightalign"> <a href="../../documentation/1.4/applications/tomcat.html" class="media" title="documentation:1.4:applications:tomcat"><img src="../../../media/applications/tomcat_logo.png" class="media" alt="" /></a> </td><td class="col2 centeralign"> <a href="../../documentation/1.4/applications/nginx.html" class="media" title="documentation:1.4:applications:nginx"><img src="../../../media/applications/nginx_logo.png" class="media" alt="" /></a> </td>
<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>
</tr>
<tr class="row2 roweven">
<th class="col0 centeralign" colspan="3"> Some applications using it </th>
@ -152,7 +152,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<p>
<p><div class="noteclassic">This requires to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a>.
<p><div class="noteclassic">This requires to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>.
</div></p>
</p>
@ -161,7 +161,7 @@ Applications listed bellow are known to be easy to integrate in <acronym title="
<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>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/googleapps.html" class="media" title="documentation:1.4: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/1.4/applications/cornerstone.html" class="media" title="documentation:1.4:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 leftalign"> <a href="../../documentation/1.4/applications/salesforce.html" class="media" title="documentation:1.4:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
<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>
</tr>
</table>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/http_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aauthbasic" class="media" title="applications:http_logo.png"><img src="../../../../media/applications/http_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -56,7 +56,7 @@ So <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Basic Autenticat
<ul>
<li class="level1"><div class="li"> Data should not contains accents or special characters, as <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> protocol only allow <acronym title="American Standard Code for Information Interchange">ASCII</acronym> values in header (but depending on the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> server, you can use <acronym title="International Organization for Standardization">ISO</acronym> 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/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4: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/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>
</ul>
@ -71,7 +71,7 @@ The Basic Authentication relies on a specific <acronym title="Hyper Text Transfe
</p>
<p>
For example, to forward login (<code>$uid</code>) and password (<code>$_password</code> if <a href="../../../documentation/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4:passwordstore">password is stored in session</a>):
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>):
</p>
<pre class="code">
@ -79,7 +79,7 @@ Authorization =&gt; &quot;Basic &quot;.encode_base64(&quot;$uid:$_password&quot;
</pre>
<p>
<acronym title="LemonLDAP::NG">LL::NG</acronym> provides a special function named <a href="../../../documentation/1.4/extendedfunctions.html#basic" class="wikilink1" title="documentation:1.4:extendedfunctions">basic</a> to build this header.
<acronym title="LemonLDAP::NG">LL::NG</acronym> 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.
</p>
<p>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/bugzilla_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Abugzilla" class="media" title="applications:bugzilla_logo.png"><img src="../../../../media/applications/bugzilla_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -88,7 +88,7 @@ Then set:
<p>
Configure Bugzilla virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure Bugzilla virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> bugzilla.example.com
@ -106,15 +106,15 @@ Configure Bugzilla virtual host like other <a href="../../../documentation/1.4/c
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Bugzilla.
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.
</p>
<p>
Configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
<p>
Configure the following <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">headers</a>.
Configure the following <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a>.
</p>
<ul>
<li class="level1"><div class="li"> <strong>Auth-User</strong>: $uid</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/csod_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Acornerstone" class="media" title="applications:csod_logo.png"><img src="../../../../media/applications/csod_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -46,7 +46,7 @@ To work with <acronym title="LemonLDAP::NG">LL::NG</acronym> it requires:
<ul>
<li class="level1"><div class="li"> An enterprise account</div>
</li>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a></div>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0: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 <acronym title="LemonLDAP::NG">LL::NG</acronym> (email will be the NameID exchanged between CSOD and <acronym title="LemonLDAP::NG">LL::NG</acronym>)</div>
</li>
@ -64,7 +64,7 @@ To work with <acronym title="LemonLDAP::NG">LL::NG</acronym> it requires:
<p>
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a>,
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>,
</p>
<p>
@ -124,7 +124,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%3A1.4%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%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>
</p>
<p>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/dokuwiki_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Adokuwiki" class="media" title="applications:dokuwiki_logo.png"><img src="../../../../media/applications/dokuwiki_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -87,7 +87,7 @@ Edit Dokuwiki local configuration (<code>conf/local.php</code>) and set <code>le
<p>
Configure Dokuwiki virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure Dokuwiki virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> dokuwiki.example.com
@ -99,7 +99,7 @@ Configure Dokuwiki virtual host like other <a href="../../../documentation/1.4/c
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
<p>
<p><div class="noteimportant">If you are protecting Dokuwiki with <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, <a href="../../../documentation/1.4/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.4:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
<p><div class="noteimportant">If you are protecting Dokuwiki with <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>.
</div></p>
</p>
@ -110,15 +110,15 @@ Configure Dokuwiki virtual host like other <a href="../../../documentation/1.4/c
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Dokuwiki.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
<p>
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">header</a>, else no headers are needed.
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> 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.
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/drupal_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Adrupal" class="media" title="applications:drupal_logo.png"><img src="../../../../media/applications/drupal_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -72,7 +72,7 @@ Go on Drupal administration interface and enable the Webserver Auth module.
<p>
Configure Drupal virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure Drupal virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> drupal.example.com
@ -84,7 +84,7 @@ Configure Drupal virtual host like other <a href="../../../documentation/1.4/con
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
<p>
<p><div class="noteimportant">If you are protecting Drupal with <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, <a href="../../../documentation/1.4/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.4:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
<p><div class="noteimportant">If you are protecting Drupal with <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>.
</div></p>
</p>
@ -95,15 +95,15 @@ Configure Drupal virtual host like other <a href="../../../documentation/1.4/con
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Drupal.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
<p>
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">header</a>, else no headers are needed.
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> 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.
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/googleapps_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Agoogleapps" class="media" title="applications:googleapps_logo.png"><img src="../../../../media/applications/googleapps_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -46,7 +46,7 @@ To work with <acronym title="LemonLDAP::NG">LL::NG</acronym> 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"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a></div>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0: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 <acronym title="LemonLDAP::NG">LL::NG</acronym> (email will be the NameID exchanged between Google Apps and <acronym title="LemonLDAP::NG">LL::NG</acronym>)</div>
</li>
@ -73,7 +73,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%3A1.4%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%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-menu.png"><img src="../../../../media/documentation/googleapps-menu.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -81,7 +81,7 @@ Then select <code>Set up single sign-on (<acronym title="Single Sign On">SSO</ac
</p>
<p>
<a href="/_detail/documentation/googleapps-sso.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-sso.png"><img src="../../../../media/documentation/googleapps-sso.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -89,7 +89,7 @@ Now configure all <acronym title="Security Assertion Markup Language">SAML</acro
</p>
<p>
<a href="/_detail/documentation/googleapps-ssoconfig.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-ssoconfig.png"><img src="../../../../media/documentation/googleapps-ssoconfig.png" class="mediacenter" alt="" /></a>
</p>
<ul>
@ -114,7 +114,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%3A1.4%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%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>
</p>
<p>
@ -141,7 +141,7 @@ You can now the upload the certificate (<code>cert.pem</code>) on Google Apps.
<p>
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a>,
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>,
</p>
<p>
@ -178,11 +178,11 @@ Now we will add Google Apps as a new <acronym title="Security Assertion Markup L
<p>
You can add a link in <a href="../../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4:portalmenu">application menu</a> to display Google Apps to users.
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.
</p>
<p>
<a href="/_detail/documentation/googleapps-manager-application.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Agoogleapps" class="media" title="documentation:googleapps-manager-application.png"><img src="../../../../media/documentation/googleapps-manager-application.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -212,11 +212,11 @@ Google Apps does not support Single Logout (SLO).
</p>
<p>
Google Apps has a configuration parameter to redirect user on a specific <acronym title="Uniform Resource Locator">URL</acronym> after Google Apps logout (see <a href="#google_apps_control_panel" title="documentation:1.4:applications:googleapps &crarr;" class="wikilink1">Google Apps control panel</a>).
Google Apps has a configuration parameter to redirect user on a specific <acronym title="Uniform Resource Locator">URL</acronym> after Google Apps logout (see <a href="#google_apps_control_panel" title="documentation:2.0:applications:googleapps &crarr;" class="wikilink1">Google Apps control panel</a>).
</p>
<p>
To manage the other way (<acronym title="LemonLDAP::NG">LL::NG</acronym> → Google Apps), you can add a dedicated <a href="../../../documentation/1.4/logoutforward.html" class="wikilink1" title="documentation:1.4:logoutforward">logout forward rule</a>:
To manage the other way (<acronym title="LemonLDAP::NG">LL::NG</acronym> → 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>:
</p>
<pre class="code">

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/liferay_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="applications:liferay_logo.png"><img src="../../../../media/applications/liferay_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -80,7 +80,7 @@ Access to Liferay (first time):
</p>
<p>
<a href="/_detail/documentation/liferay_1.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_1.png"><img src="../../../../media/documentation/liferay_1.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -88,7 +88,7 @@ Login as administrator:
</p>
<p>
<a href="/_detail/documentation/liferay_2.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_2.png"><img src="../../../../media/documentation/liferay_2.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -96,7 +96,7 @@ Go to <code>My Account</code>:
</p>
<p>
<a href="/_detail/documentation/liferay_3.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_3.png"><img src="../../../../media/documentation/liferay_3.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -104,7 +104,7 @@ Go to <code>Portal</code> » <code>Settings</code>:
</p>
<p>
<a href="/_detail/documentation/liferay_4.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_4.png"><img src="../../../../media/documentation/liferay_4.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -112,7 +112,7 @@ Go to <code>Configuration</code> » <code>Authentication</code>:
</p>
<p>
<a href="/_detail/documentation/liferay_5.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_5.png"><img src="../../../../media/documentation/liferay_5.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -130,7 +130,7 @@ In <code>General</code>, fill at least the following information:
</p>
<p>
<a href="/_detail/documentation/liferay_6.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_6.png"><img src="../../../../media/documentation/liferay_6.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -154,7 +154,7 @@ Then use the <code>SiteMinder</code> tab to configure <acronym title="Single Sig
<ul>
<li class="level1"><div class="li"> <strong>Enabled</strong>: Yes</div>
</li>
<li class="level1"><div class="li"> <strong>Import from <acronym title="Lightweight Directory Access Protocol">LDAP</acronym></strong>: Yes (see <a href="#presentation" title="documentation:1.4:applications:liferay &crarr;" class="wikilink1">presentation</a>)</div>
<li class="level1"><div class="li"> <strong>Import from <acronym title="Lightweight Directory Access Protocol">LDAP</acronym></strong>: Yes (see <a href="#presentation" title="documentation:2.0:applications:liferay &crarr;" class="wikilink1">presentation</a>)</div>
</li>
<li class="level1"><div class="li"> <strong>User Header</strong>: Auth-User (case sensitive)</div>
</li>
@ -162,7 +162,7 @@ Then use the <code>SiteMinder</code> tab to configure <acronym title="Single Sig
<p>
<a href="/_detail/documentation/liferay_7.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aliferay" class="media" title="documentation:liferay_7.png"><img src="../../../../media/documentation/liferay_7.png" class="mediacenter" alt="" width="600" /></a>
</p>
<p>
@ -177,7 +177,7 @@ Then use the <code>SiteMinder</code> tab to configure <acronym title="Single Sig
<p>
Configure Liferay virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure Liferay virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> liferay.example.com
@ -195,11 +195,11 @@ Configure Liferay virtual host like other <a href="../../../documentation/1.4/co
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Liferay.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>. You can add a rule for logout:
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:
</p>
<pre class="code">
@ -207,7 +207,7 @@ Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.h
</pre>
<p>
Configure the <code>Auth-User</code> <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">header</a>.
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>.
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/limesurvey_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Alimesurvey" class="media" title="applications:limesurvey_logo.png"><img src="../../../../media/applications/limesurvey_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -109,7 +109,7 @@ vi /var/www/html/limesurvey/config.php
<p>
Configure LimeSurvey virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure LimeSurvey virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> limesurvey.example.com
@ -135,7 +135,7 @@ Configure LimeSurvey virtual host like other <a href="../../../documentation/1.4
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for LimeSurvey.
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.
</p>
</div>
@ -165,7 +165,7 @@ Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemon
<p>
<p><div class="notetip">You can manage roles with the <a href="../../../documentation/1.4/rbac.html" class="wikilink1" title="documentation:1.4:rbac">RBAC model</a> or by using groups.
<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.
</div></p>
</p>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/mediawiki_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Amediawiki" class="media" title="applications:mediawiki_logo.png"><img src="../../../../media/applications/mediawiki_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -117,7 +117,7 @@ vi LocalSettings.php
<p>
Configure MediaWiki virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure MediaWiki virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> mediawiki.example.com
@ -129,7 +129,7 @@ Configure MediaWiki virtual host like other <a href="../../../documentation/1.4/
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
<p>
<p><div class="noteimportant">If you are protecting MediaWiki with <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, <a href="../../../documentation/1.4/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.4:header_remote_user_conversion">convert header into REMOTE_USER environment variable</a>.
<p><div class="noteimportant">If you are protecting MediaWiki with <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>.
</div></p>
</p>
@ -140,11 +140,11 @@ Configure MediaWiki virtual host like other <a href="../../../documentation/1.4/
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for MediaWiki.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>. You can also add a rule for logout:
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:
</p>
<pre class="code">
@ -152,7 +152,7 @@ Userlogout =&gt; logout_sso
</pre>
<p>
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> as reverse proxy, configure the <code>Auth-User</code> <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">header</a>, else no headers are needed.
If using <acronym title="LemonLDAP::NG">LL::NG</acronym> 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.
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/obm_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aobm" class="media" title="applications:obm_logo.png"><img src="../../../../media/applications/obm_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -174,7 +174,7 @@ Edit also OBM Apache configuration to enable <acronym title="LemonLDAP::NG">LL::
&lt;/<span class="kw3">VirtualHost</span>&gt;</pre>
<p>
<p><div class="noteimportant">OBM Apache configuration must be loaded <strong>after</strong> <acronym title="LemonLDAP::NG">LL::NG</acronym> <a href="../../../documentation/1.4/configlocation.html#apache" class="wikilink1" title="documentation:1.4:configlocation">Apache configuration</a>.
<p><div class="noteimportant">OBM Apache configuration must be loaded <strong>after</strong> <acronym title="LemonLDAP::NG">LL::NG</acronym> <a href="../../../documentation/2.0/configlocation.html#apache" class="wikilink1" title="documentation:2.0:configlocation">Apache configuration</a>.
</div></p>
</p>
@ -211,7 +211,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&#039;s password to OBM, then you have to <a href="../../../documentation/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4:passwordstore">keep the password in session</a>.
<p><div class="noteimportant">If you plan to forward user&#039;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>.
</div></p>
</p>
@ -322,7 +322,7 @@ Define headers used in OBM mapping, for example:
<p>
Do not forget to add OBM in <a href="../../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4:portalmenu">applications menu</a>.
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>.
</p>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/phpldapadmin_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aphpldapadmin" class="media" title="applications:phpldapadmin_logo.png"><img src="../../../../media/applications/phpldapadmin_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -74,7 +74,7 @@ Just set the authentication type to <code>config</code> and indicate <acronym ti
<p>
Configure phpLDAPadmin virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a>.
Configure phpLDAPadmin virtual host like other <a href="../../../documentation/2.0/configvhost.html" class="wikilink1" title="documentation:2.0:configvhost">protected virtual host</a>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> phpldapadmin.example.com
@ -92,15 +92,15 @@ Configure phpLDAPadmin virtual host like other <a href="../../../documentation/1
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for phpLDAPadmin.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
<p>
No <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">headers</a> are required.
No <a href="../../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">headers</a> are required.
</p>

@ -59,7 +59,7 @@
</ul>
<p>
<p><div class="noteclassic">To be able to forward password to RoundCube, see <a href="../../../documentation/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4:passwordstore">how to store password in session</a>
<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>
</div></p>
</p>
<ul>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/salesforce-logo.jpg?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Asalesforce" class="media" title="applications:salesforce-logo.jpg"><img src="../../../../media/applications/salesforce-logo.jpg" class="mediacenter" alt="" /></a>
</p>
</div>
@ -37,7 +37,7 @@
<p>
<a href="../../../documentation/1.4/applications.html" class="wikilink1" title="documentation:1.4:applications">Salesforce</a> Salesforce Inc. is a cloud computing company. It is best known for their CRM products and social networking applications.
<a href="../../../documentation/2.0/applications.html" class="wikilink1" title="documentation:2.0:applications">Salesforce</a> Salesforce Inc. is a cloud computing company. It is best known for their CRM products and social networking applications.
</p>
<p>
@ -52,7 +52,7 @@ This page presents the SP initiated mode.
To work with <acronym title="LemonLDAP::NG">LL::NG</acronym> it requires:
</p>
<ul>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a></div>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> configured as <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></div>
</li>
</ul>
@ -63,7 +63,7 @@ To work with <acronym title="LemonLDAP::NG">LL::NG</acronym> it requires:
<p>
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as a <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a>.
You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as a <a href="../../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a>.
</p>
</div>
@ -73,7 +73,7 @@ You should have configured <acronym title="LemonLDAP::NG">LL::NG</acronym> as a
<p>
<a href="/_detail/applications/my_domain_salesforce-resize-web.png?id=documentation%3A1.4%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%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>
</p>
<p>
@ -118,7 +118,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%3A1.4%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%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>
</p>
<p>
@ -172,7 +172,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%3A1.4%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%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>
</p>
<p>
@ -180,7 +180,7 @@ Once this is completed, click to export the Salesforce metadata and import them
</p>
<p>
See <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">Register partner Service Provider on LemonLDAP::NG</a> configuration chapter.
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.
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/spring_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Aspring" class="media" title="applications:spring_logo.png"><img src="../../../../media/applications/spring_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/sympa_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Asympa" class="media" title="applications:sympa_logo.png"><img src="../../../../media/applications/sympa_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -89,7 +89,7 @@ Choose one of the following method:
<p>
Configure Sympa virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a> but use Sympa Handler instead of default Handler.
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.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> sympa.example.com
@ -109,11 +109,11 @@ Configure Sympa virtual host like other <a href="../../../documentation/1.4/conf
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Sympa.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
</div>
@ -187,7 +187,7 @@ You can also use &lt;portal&gt;?logout=1 as logout_url to remove LemonLDAP::NG s
<p>
Configure Sympa virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a> but protect only magic authentication <acronym title="Uniform Resource Locator">URL</acronym>.
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 <acronym title="Uniform Resource Locator">URL</acronym>.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> sympa.example.com
@ -212,11 +212,11 @@ Configure Sympa virtual host like other <a href="../../../documentation/1.4/conf
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Sympa.
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.
</p>
<p>
Configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a> and define the following <a href="../../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">headers</a>:
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>:
</p>
<ul>
<li class="level1"><div class="li"> Auth-User</div>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/tomcat_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Atomcat" class="media" title="applications:tomcat_logo.png"><img src="../../../../media/applications/tomcat_logo.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -82,7 +82,7 @@ cp ValveLemonLDAPNG.jar server/lib/
</pre>
<p>
<p><div class="notetip">If needed, you can <a href="#compilation" title="documentation:1.4:applications:tomcat &crarr;" class="wikilink1">recompile the valve from the sources</a>.
<p><div class="notetip">If needed, you can <a href="#compilation" title="documentation:2.0:applications:tomcat &crarr;" class="wikilink1">recompile the valve from the sources</a>.
</div></p>
</p>

@ -27,7 +27,7 @@
<p>
<a href="/_detail/applications/zimbra_logo.png?id=documentation%3A1.4%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%3A2.0%3Aapplications%3Azimbra" class="media" title="applications:zimbra_logo.png"><img src="../../../../media/applications/zimbra_logo.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -45,7 +45,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 <acronym title="LemonLDAP::NG">LL::NG</acronym> via <a href="../../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4: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 <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>).
</div></p>
</p>
@ -90,7 +90,7 @@ See <a href="http://wiki.zimbra.com/index.php?title=Preauth#Preparing_a_domain_f
<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 <acronym title="Single Sign On">SSO</acronym> <acronym title="Uniform Resource Locator">URL</acronym> and <a href="../../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4: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 <acronym title="Single Sign On">SSO</acronym> <acronym title="Uniform Resource Locator">URL</acronym> and <a href="../../../documentation/2.0/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:2.0:portalmenu">set it in application menu</a>.
</p>
</div>
@ -100,7 +100,7 @@ Choose for example <a href="http://zimbra.example.com/zimbrasso" class="urlexter
<p>
You will configure Zimbra virtual host like other <a href="../../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4: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/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.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *&gt;
<span class="kw1">ServerName</span> zimbra.example.com
@ -119,11 +119,11 @@ You will configure Zimbra virtual host like other <a href="../../../documentatio
<p>
Go to the Manager and <a href="../../../documentation/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4:configvhost">create a new virtual host</a> for Zimbra.
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.
</p>
<p>
Just configure the <a href="../../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">access rules</a>.
Just configure the <a href="../../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">access rules</a>.
</p>
</div>

@ -40,7 +40,7 @@
<p>
The Active Directory module is based on the <a href="../../documentation/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP module</a>, with these features:
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:
</p>
<ul>
<li class="level1"><div class="li"> Specific default values for filters to match AD schema</div>
@ -58,7 +58,7 @@ The Active Directory module is based on the <a href="../../documentation/1.4/aut
<p>
The configuration is the same as the <a href="../../documentation/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP module</a>.
The configuration is the same as the <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP module</a>.
</p>

@ -287,7 +287,7 @@ Modify the portal virtual host:
<p>
You may want to use the <a href="../../documentation/1.4/authmulti.html" class="wikilink1" title="documentation:1.4:authmulti">Mutliple authentication backend</a> to fail back to another authentication for user without Kerberos ticket.
You may want to use the <a href="../../documentation/2.0/authmulti.html" class="wikilink1" title="documentation:2.0:authmulti">Mutliple authentication backend</a> to fail back to another authentication for user without Kerberos ticket.
</p>
<p>

@ -50,7 +50,7 @@ In Manager, go in <code>General Parameters</code> &gt; <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/1.4/authnull.html" class="wikilink1" title="documentation:1.4: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/2.0/authnull.html" class="wikilink1" title="documentation:2.0:authnull">None</a> for users and password.
</div></p>
</p>

@ -44,7 +44,7 @@
</p>
<p>
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> can also act as <a href="../../documentation/1.4/idpcas.html" class="wikilink1" title="documentation:1.4:idpcas">CAS server</a>, that allows to interconnect two <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> 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 <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
</div></p>
</p>
@ -57,11 +57,11 @@
</p>
<p>
They can then be forwarded to applications trough <a href="../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">HTTP headers</a>.
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>.
</p>
<p>
<p><div class="notetip"><acronym title="Central Authentication Service">CAS</acronym> authentication will automatically add a <a href="../../documentation/1.4/logoutforward.html" class="wikilink1" title="documentation:1.4:logoutforward">logout forward rule</a> on <acronym title="Central Authentication Service">CAS</acronym> server logout <acronym title="Uniform Resource Locator">URL</acronym> in order to close <acronym title="Central Authentication Service">CAS</acronym> session on <acronym title="LemonLDAP::NG">LL::NG</acronym> logout.
<p><div class="notetip"><acronym title="Central Authentication Service">CAS</acronym> authentication will automatically add a <a href="../../documentation/2.0/logoutforward.html" class="wikilink1" title="documentation:2.0:logoutforward">logout forward rule</a> on <acronym title="Central Authentication Service">CAS</acronym> server logout <acronym title="Uniform Resource Locator">URL</acronym> in order to close <acronym title="Central Authentication Service">CAS</acronym> session on <acronym title="LemonLDAP::NG">LL::NG</acronym> logout.
</div></p>
</p>

@ -44,7 +44,7 @@ By default, only the configured authentication backend is available for users.
</p>
<p>
Contrary to <a href="../../documentation/1.4/authmulti.html" class="wikilink1" title="documentation:1.4: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/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.
</p>
<p>
@ -107,7 +107,7 @@ Then, go in <code>Choice Parameters</code>:
<p>
<a href="/_detail/documentation/manager-authchoice.png?id=documentation%3A1.4%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%3A2.0%3Aauthchoice" class="media" title="documentation:manager-authchoice.png"><img src="../../../media/documentation/manager-authchoice.png" class="mediacenter" alt="" /></a>
</p>
<p>

@ -204,7 +204,7 @@ As <acronym title="Database Interface">DBI</acronym> is a login/password based m
<ul>
<li class="level1"><div class="li"> increased (+1) if portal is protected by <acronym title="Secure Sockets Layer">SSL</acronym> (HTTPS)</div>
</li>
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/1.4/portalcustom.html" class="wikilink1" title="documentation:1.4:portalcustom">portal customization</a>)</div>
<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>
</ul>
@ -220,7 +220,7 @@ As <acronym title="Database Interface">DBI</acronym> is a login/password based m
<p>
List of columns to query to fill user session. See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
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>.
</p>
</div>

@ -88,7 +88,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/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4: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/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>
</div>

@ -86,7 +86,7 @@ If you use Facebook as user database, declare values in exported variables :
<p>
See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>
<p>

@ -83,7 +83,7 @@ Use the name you want but this values in the value field. If you want to require
<p>
See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>
<p>

@ -55,7 +55,7 @@
<p>
This works with every <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> v2 or v3 server, including <a href="../../documentation/1.4/authad.html" class="wikilink1" title="documentation:1.4:authad">Active Directory</a>.
This works with every <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> v2 or v3 server, including <a href="../../documentation/2.0/authad.html" class="wikilink1" title="documentation:2.0:authad">Active Directory</a>.
</p>
<p>
@ -82,7 +82,7 @@ In Manager, go in <code>General Parameters</code> &gt; <code>Authentication modu
<p>
<p><div class="notetip">
For <a href="../../documentation/1.4/authad.html" class="wikilink1" title="documentation:1.4:authad">Active Directory</a>, choose <code>Active Directory</code> instead of <code><acronym title="Lightweight Directory Access Protocol">LDAP</acronym></code>.
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><acronym title="Lightweight Directory Access Protocol">LDAP</acronym></code>.
</div></p>
</p>
@ -103,7 +103,7 @@ As <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> is a lo
<ul>
<li class="level1"><div class="li"> increased (+1) if portal is protected by <acronym title="Secure Sockets Layer">SSL</acronym> (HTTPS)</div>
</li>
<li class="level1"><div class="li"> decreased (-1) if the portal autocompletion is allowed (see <a href="../../documentation/1.4/portalcustom.html" class="wikilink1" title="documentation:1.4:portalcustom">portal customization</a>)</div>
<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>
</ul>
@ -119,7 +119,7 @@ As <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> is a lo
<p>
List of attributes to query to fill user session. See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
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>.
</p>
</div>
@ -228,11 +228,11 @@ And the mail filter is:
</li>
<li class="level1"><div class="li"> <strong>Password modify extended operation</strong>: enable to use the <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> 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/1.4/portalcustom.html" class="wikilink1" title="documentation:1.4: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/2.0/portalcustom.html" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>).</div>
</li>
<li class="level1"><div class="li"> <strong><acronym title="Lightweight Directory Access Protocol">LDAP</acronym> password encoding</strong>: can allow to manage old <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> 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/1.4/resetpassword.html" class="wikilink1" title="documentation:1.4: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/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>
<li class="level1"><div class="li"> <strong>Reset attribute</strong>: name of password reset attribute (default: pwdReset).</div>
</li>
@ -251,7 +251,7 @@ Standards attributes, like uid, cn or mail, are often enough to configure access
</p>
<p>
But sometimes other data are needed (in particular to use <a href="../../documentation/1.4/extendedfunctions.html" class="wikilink1" title="documentation:1.4:extendedfunctions">extended functions</a>):
But sometimes other data are needed (in particular to use <a href="../../documentation/2.0/extendedfunctions.html" class="wikilink1" title="documentation:2.0:extendedfunctions">extended functions</a>):
</p>
<ul>
<li class="level1"><div class="li"> An application name (to allow access by applications and not by group of users)</div>
@ -318,7 +318,7 @@ You can add this object class to any entry of your directory.
</p>
<p>
<p><div class="noteimportant">To get attributes values in session, declare them in <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables</a>
<p><div class="noteimportant">To get attributes values in session, declare them in <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables</a>
</div></p>
</p>

@ -89,7 +89,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 <acronym title="LemonLDAP::NG">LL::NG</acronym> <a href="../../documentation/1.4/parameterlist.html" class="wikilink1" title="documentation:1.4:parameterlist">parameter</a> when a specific backend is used</div>
<li class="level1"><div class="li"> overload any <acronym title="LemonLDAP::NG">LL::NG</acronym> <a href="../../documentation/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter</a> when a specific backend is used</div>
</li>
</ul>
@ -108,7 +108,7 @@ Multi LDAP#Openldap; LDAP#ActiveDirectory
</pre>
<p>
Then you can have different <a href="../../documentation/1.4/parameterlist.html" class="wikilink1" title="documentation:1.4:parameterlist">parameters</a> for each stored in a <acronym title="Practical Extraction and Report Language">Perl</acronym> hash entry named multi:
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 <acronym title="Practical Extraction and Report Language">Perl</acronym> hash entry named multi:
</p>
<pre class="code perl">multi <span class="sy0">=&gt;</span> <span class="br0">&#123;</span>
@ -164,7 +164,7 @@ When using this module, <acronym title="LemonLDAP::NG">LL::NG</acronym> portal w
</p>
<p>
To bypass this, follow the documentation of <a href="../../documentation/1.4/authapache.html#use_kerberos_with_multiple_authentication_backend" class="wikilink1" title="documentation:1.4:authapache">AuthApache module</a>
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>
</p>
</div>

@ -44,7 +44,7 @@
</p>
<p>
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> can also act as <a href="../../documentation/1.4/idpopenid.html" class="wikilink1" title="documentation:1.4:idpopenid">OpenID server</a>, that allows to interconnect two <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> 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 <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
</div></p>
</p>
@ -53,7 +53,7 @@
</p>
<p>
<p><div class="notetip">OpenID authentication can proposed as an alternate authentication scheme using the <a href="../../documentation/1.4/authchoice.html" class="wikilink1" title="documentation:1.4:authchoice">authentication choice</a> method.
<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.
</div></p>
</p>
@ -126,7 +126,7 @@ To configure requested attributes, edit <strong>Exported variables</strong> and
<p>
See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>

@ -44,7 +44,7 @@
</p>
<p>
The difference with <a href="../../documentation/1.4/authremote.html" class="wikilink1" title="documentation:1.4:authremote">remote authentication</a> is that the client will never be redirect to the main <acronym title="LemonLDAP::NG">LL::NG</acronym> portal. This configuration is usable if you want to expose your internal <acronym title="Single Sign On">SSO</acronym> portal to another network (DMZ).
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 <acronym title="LemonLDAP::NG">LL::NG</acronym> portal. This configuration is usable if you want to expose your internal <acronym title="Single Sign On">SSO</acronym> portal to another network (DMZ).
</p>
</div>
@ -81,7 +81,7 @@ Then, go in <code>Proxy parameters</code>:
<p>
The portal must be configured to accept <acronym title="Simple Object Access Protocol">SOAP</acronym> authentication requests. See <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4:soapsessionbackend">SOAP session backend</a> documentation.
The portal must be configured to accept <acronym title="Simple Object Access Protocol">SOAP</acronym> authentication requests. See <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP session backend</a> documentation.
</p>
</div>

@ -35,7 +35,7 @@
<p>
<p><div class="notetip">This module is a <acronym title="LemonLDAP::NG">LL::NG</acronym> specific identity federation protocol. You may rather use standards protocols like <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML</a>, <a href="../../documentation/1.4/idpopenid.html" class="wikilink1" title="documentation:1.4:idpopenid">OpenID</a> or <a href="../../documentation/1.4/idpcas.html" class="wikilink1" title="documentation:1.4:idpcas">CAS</a>.
<p><div class="notetip">This module is a <acronym title="LemonLDAP::NG">LL::NG</acronym> 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/idpopenid.html" class="wikilink1" title="documentation:2.0:idpopenid">OpenID</a> or <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS</a>.
</div></p>
</p>
@ -46,7 +46,7 @@
<ul>
<li class="level1"><div class="li"> The main portal is configured to use <acronym title="Cross Domain Authentication">CDA</acronym>. The secondary portal is declared in the Manager of the main <acronym title="LemonLDAP::NG">LL::NG</acronym> structure (else user will be rejected).</div>
</li>
<li class="level1"><div class="li"> The portal of the secondary <acronym title="LemonLDAP::NG">LL::NG</acronym> structure is configured to delegate authentication to a remote portal. A request to the main session database is done (trough <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4:soapsessionbackend">SOAP session backend</a>) to be sure that the session exists.</div>
<li class="level1"><div class="li"> The portal of the secondary <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>
<li class="level1"><div class="li"> If <code>exportedAttr</code> is set, only those attributes are copied in the session database of the secondary <acronym title="LemonLDAP::NG">LL::NG</acronym> structure. Else, all data are copied in the session database.</div>
</li>
@ -54,7 +54,7 @@
<p>
<a href="/_detail/documentation/remote-principle.png?id=documentation%3A1.4%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%3A2.0%3Aauthremote" class="media" title="documentation:remote-principle.png"><img src="../../../media/documentation/remote-principle.png" class="mediacenter" alt="" /></a>
</p>
<ol>
@ -121,11 +121,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::<acronym title="Simple Object Access Protocol">SOAP</acronym></code> for <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4:soapsessionbackend">SOAP session backend</a>.</div>
<li class="level1"><div class="li"> <strong>Sessions module</strong>: set <code>Lemonldap::NG::Common::Apache::Session::<acronym title="Simple Object Access Protocol">SOAP</acronym></code> for <a href="../../documentation/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0: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>: <acronym title="Simple Object Access Protocol">SOAP</acronym> sessions end point (see <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4:soapsessionbackend">SOAP session backend</a> documentation)</div>
<li class="level2"><div class="li"> <strong>proxy</strong>: <acronym title="Simple Object Access Protocol">SOAP</acronym> 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>
</ul>
</li>
@ -159,7 +159,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%3A1.4%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%3A2.0%3Aauthremote" class="media" title="documentation:remote-interoperability.png"><img src="../../../media/documentation/remote-interoperability.png" class="mediacenter" alt="" /></a>
</p>
<ol>

@ -52,7 +52,7 @@ For each IDP, you can configure attributes that are collected. Some can be manda
</p>
<p>
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> can also act as <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML IDP</a>, that allows to interconnect two <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
<p><div class="notetip"><acronym title="LemonLDAP::NG">LL::NG</acronym> 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 <acronym title="LemonLDAP::NG">LL::NG</acronym> systems.
</div></p>
</p>
@ -68,7 +68,7 @@ For each IDP, you can configure attributes that are collected. Some can be manda
<p>
See <a href="../../documentation/1.4/samlservice.html" class="wikilink1" title="documentation:1.4:samlservice">SAML service</a> configuration chapter.
See <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service</a> configuration chapter.
</p>
</div>
@ -89,7 +89,7 @@ In <code>General Parameters</code> &gt; <code>Authentication modules</code>, set
<p>
<p><div class="notetip">As passwords will not be managed by <acronym title="LemonLDAP::NG">LL::NG</acronym>, you can disable <a href="../../documentation/1.4/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.4:portalmenu">menu password module</a>.
<p><div class="notetip">As passwords will not be managed by <acronym title="LemonLDAP::NG">LL::NG</acronym>, you can disable <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0:portalmenu">menu password module</a>.
</div></p>
</p>
@ -118,7 +118,7 @@ In the Manager, select node <code><acronym title="Security Assertion Markup Lang
</p>
<p>
<a href="/_detail/documentation/manager-saml-idp-new.png?id=documentation%3A1.4%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%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>
</p>
<p>
@ -130,7 +130,7 @@ Now you have access to the IDP parameters list:
</p>
<p>
<a href="/_detail/documentation/manager-saml-idp-list.png?id=documentation%3A1.4%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%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>
</p>
</div>
@ -144,7 +144,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%3A1.4%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%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>
</p>
<p>
@ -176,7 +176,7 @@ For each attribute, you can set:
<p>
<a href="/_detail/documentation/manager-saml-idp-attribute.png?id=documentation%3A1.4%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%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>
</p>
</div>
@ -217,7 +217,7 @@ $ENV{REMOTE_ADDR} =~ /^192\.168/
</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/1.4/samlservice.html#authentication_contexts" class="wikilink1" title="documentation:1.4: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/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>
</ul>
@ -239,7 +239,7 @@ $ENV{REMOTE_ADDR} =~ /^192\.168/
<p>
These options override service signature options (see <a href="../../documentation/1.4/samlservice.html#general_options" class="wikilink1" title="documentation:1.4:samlservice">SAML service configuration</a>).
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>).
</p>
<ul>
<li class="level1"><div class="li"> <strong>Sign <acronym title="Single Sign On">SSO</acronym> message</strong>: sign <acronym title="Single Sign On">SSO</acronym> message</div>

@ -96,7 +96,7 @@ You have then to declare <acronym title="Hyper Text Transfer Protocol">HTTP</acr
<p>
See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>

@ -40,7 +40,7 @@
<p>
<acronym title="LemonLDAP::NG">LL::NG</acronym> 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.4/authapache.html" class="wikilink1" title="documentation:1.4:authapache">Apache authentication module</a>, with extra features:
<acronym title="LemonLDAP::NG">LL::NG</acronym> 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:
</p>
<ul>
<li class="level1"><div class="li"> Choice of any certificate attribute as user main login</div>
@ -141,7 +141,7 @@ All <acronym title="Secure Sockets Layer">SSL</acronym> options are documented i
Here are the main options used by <acronym title="LemonLDAP::NG">LL::NG</acronym>:
</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 <acronym title="LemonLDAP::NG">LL::NG</acronym> portal page. To switch to another authentication backend, use the <a href="../../documentation/1.4/authmulti.html" class="wikilink1" title="documentation:1.4:authmulti">Multi</a> module, for example: <code>Multi <acronym title="Secure Sockets Layer">SSL</acronym>;<acronym title="Lightweight Directory Access Protocol">LDAP</acronym></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 <acronym title="LemonLDAP::NG">LL::NG</acronym> 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 <acronym title="Secure Sockets Layer">SSL</acronym>;<acronym title="Lightweight Directory Access Protocol">LDAP</acronym></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>

@ -82,7 +82,7 @@ If you use WebID as user database, declare values in <strong>exported variables<
<p>
See also <a href="../../documentation/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4:exportedvars">exported variables configuration</a>.
See also <a href="../../documentation/2.0/exportedvars.html" class="wikilink1" title="documentation:2.0:exportedvars">exported variables configuration</a>.
</p>
</div>

@ -98,7 +98,7 @@ The following table list fields to index depending on the feature you want to in
<p>
Using Redis, you just have to prepare Redis database. See <a href="../../documentation/1.4/nosqlsessionbackend.html" class="wikilink1" title="documentation:1.4:nosqlsessionbackend">Redis session backend</a>.
Using Redis, you just have to prepare Redis database. See <a href="../../documentation/2.0/nosqlsessionbackend.html" class="wikilink1" title="documentation:2.0:nosqlsessionbackend">Redis session backend</a>.
</p>
<p>
@ -106,7 +106,7 @@ Using Redis, you just have to prepare Redis database. See <a href="../../documen
</p>
<p>
Database must be prepared exactly like in <a href="../../documentation/1.4/sqlsessionbackend.html#prepare_the_database" class="wikilink1" title="documentation:1.4: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/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.
</p>
<pre class="code file sql"><span class="kw1">CREATE</span> <span class="kw1">TABLE</span> sessions <span class="br0">&#40;</span>
id char<span class="br0">&#40;</span>32<span class="br0">&#41;</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>

@ -53,7 +53,7 @@ We use the <acronym title="Practical Extraction and Report Language">Perl</acron
</p>
<p>
<a href="/_detail/documentation/captcha.png?id=documentation%3A1.4%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%3A2.0%3Acaptcha" class="media" title="documentation:captcha.png"><img src="../../../media/documentation/captcha.png" class="mediacenter" alt="" /></a>
</p>
</div>

@ -76,13 +76,13 @@ The <code>convertConfig</code> utility reads 2 <acronym title="LemonLDAP::NG">LL
Documentation is available for configuration backends :
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">SQL</a></div>
<li class="level1"><div class="li"> <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">SQL</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File</a></div>
<li class="level1"><div class="li"> <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP</a></div>
<li class="level1"><div class="li"> <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP</a></div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP proxy mechanism</a></div>
<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>
</ul>

@ -47,16 +47,16 @@ LemonLDAP::NG configuration is stored in a backend that allows all modules to ac
<p>
Detailled configuration backends documentation is available <a href="../../documentation/1.4/start.html#configuration_database" class="wikilink1" title="documentation:1.4:start">here</a>.
Detailled configuration backends documentation is available <a href="../../documentation/2.0/start.html#configuration_database" class="wikilink1" title="documentation:2.0:start">here</a>.
</div></p>
</p>
<p>
By default, configuration is stored in <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">files</a>, so access trough network is not possible. To allow this, use <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP</a> for configuration access, or use a network service like <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">SQL database</a> or <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP directory</a>.
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>.
</p>
<p>
Configuration backend can be set in the <a href="#local_file" title="documentation:1.4:configlocation &crarr;" class="wikilink1">local configuration file</a>, in <code>configuration</code> section.
Configuration backend can be set in the <a href="#local_file" title="documentation:2.0:configlocation &crarr;" class="wikilink1">local configuration file</a>, in <code>configuration</code> section.
</p>
<p>
@ -67,7 +67,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/1.4/changeconfbackend.html" class="wikilink1" title="documentation:1.4:changeconfbackend">How to change configuration backend</a> to known how to change this.
<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.
</div></p>
</p>
@ -107,7 +107,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/1.4/managerprotection.html" class="wikilink1" title="documentation:1.4:managerprotection">Manager protection documentation</a> to know how to use Apache modules or <acronym title="LemonLDAP::NG">LL::NG</acronym> to manage access to Manager.
<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 <acronym title="LemonLDAP::NG">LL::NG</acronym> to manage access to Manager.
</div></p>
</p>
@ -582,7 +582,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/1.4/parameterlist.html" class="wikilink1" title="documentation:1.4: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/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter list</a> to find it.
</div></p>
</p>
@ -597,7 +597,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/1.4/parameterlist.html" class="wikilink1" title="documentation:1.4: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/2.0/parameterlist.html" class="wikilink1" title="documentation:2.0:parameterlist">parameter list</a> to find it.
</div></p>
</p>

@ -37,7 +37,7 @@ LemonLDAP::NG configuration is build around Apache virtual hosts. Each virtual h
<p>
To protect a virtual host in Apache, the LemonLDAP::NG Handler must be activated (see <a href="../../documentation/1.4/configlocation.html#apache" class="wikilink1" title="documentation:1.4:configlocation">Apache global configuration</a>).
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>).
</p>
<p>
@ -116,12 +116,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/1.4/header_remote_user_conversion.html" class="wikilink1" title="documentation:1.4: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/2.0/header_remote_user_conversion.html" class="wikilink1" title="documentation:2.0: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/1.4/internalproxy.html" class="wikilink1" title="documentation:1.4:internalproxy">internal proxy</a> to replace Apache mod_proxy configuration.
<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.
</div></p>
</p>
@ -180,7 +180,7 @@ A virtual host contains:
<p>
See <strong><a href="../../documentation/1.4/writingrulesand_headers.html" class="wikilink1" title="documentation:1.4:writingrulesand_headers">Writing rules and headers</a></strong> to learn how to configure access control and <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> headers sent to application by <acronym title="LemonLDAP::NG">LL::NG</acronym>.
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 <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> headers sent to application by <acronym title="LemonLDAP::NG">LL::NG</acronym>.
</p>
</div>
@ -190,7 +190,7 @@ See <strong><a href="../../documentation/1.4/writingrulesand_headers.html" class
<p>
See <strong><a href="../../documentation/1.4/formreplay.html" class="wikilink1" title="documentation:1.4:formreplay">Form replay</a></strong> to learn how to configure form replay to POST data on protected applications.
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.
</p>
</div>

@ -27,7 +27,7 @@
<p>
Custom functions allow to extend <acronym title="LemonLDAP::NG">LL::NG</acronym>, they can be used in <a href="../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">headers</a>, <a href="../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">rules</a> or <a href="../../documentation/1.4/formreplay.html" class="wikilink1" title="documentation:1.4:formreplay">form replay data</a>.
Custom functions allow to extend <acronym title="LemonLDAP::NG">LL::NG</acronym>, 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>.
</p>
</div>
@ -105,7 +105,7 @@ SSOExtensions::function1
</pre>
<p>
<p><div class="noteimportant">If your function is not compliant with <a href="../../documentation/1.4/safejail.html" class="wikilink1" title="documentation:1.4: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/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail.
</div></p>
</p>

@ -45,7 +45,7 @@
<p>
→ When you upgrade from Debian Lenny with customized index.pl files, you must upgrade them. See <a href="../../documentation/1.4/upgrade.html#debian_lenny_upgrade" class="wikilink1" title="documentation:1.4:upgrade">Debian Lenny upgrade</a>.
→ 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>.
</p>
</div>

@ -32,7 +32,7 @@
<p>
Exported variables are the variables available to <a href="../../documentation/1.4/writingrulesand_headers.html" class="wikilink1" title="documentation:1.4:writingrulesand_headers">write rules and headers</a>. They are extracted from the users database by the <a href="../../documentation/1.4/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.4:start">users module</a>.
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>.
</p>
<p>
@ -40,7 +40,7 @@ To create a variable, you&#039;ve just to map a user attributes in <acronym titl
</p>
<p>
Examples for <a href="../../documentation/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP</a>:
Examples for <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">LDAP</a>:
</p>
<table class="inline">
<tr class="row0 roweven">
@ -68,14 +68,14 @@ You can define exported variables for each module in the module configuration it
</p>
<p>
<a href="/_detail/documentation/exportedvars.png?id=documentation%3A1.4%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%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>
</p>
</div>
<!-- SECTION "Presentation" [35-1250] -->
<h2><a name="extend_variables_using_macros_and_groups" id="extend_variables_using_macros_and_groups">Extend variables using macros and groups</a></h2>
<div class="level2">
<div class="plugin_include_content" id="plugin_include__documentation:1.4:performances">
<div class="plugin_include_content" id="plugin_include__documentation:2.0:performances">
<div class="level3">
<p>
@ -83,7 +83,7 @@ You can define exported variables for each module in the module configuration it
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/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4: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/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>
<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>

@ -32,16 +32,16 @@
<p>
When <a href="../../documentation/1.4/writingrulesand_headers.html" class="wikilink1" title="documentation:1.4:writingrulesand_headers">writing rules and headers</a>, you can use <acronym title="Practical Extraction and Report Language">Perl</acronym> expressions that will be evaluated in a jail, to prevent bad code execution.
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 <acronym title="Practical Extraction and Report Language">Perl</acronym> 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/1.4/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.4:portalmenu">Menu modules activation rules</a></div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/formreplay.html" class="wikilink1" title="documentation:1.4:formreplay">Form replay data</a></div>
<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>
<li class="level1"><div class="li"> Macros</div>
</li>
@ -58,27 +58,27 @@ Inside this jail, you can access to:
<ul>
<li class="level1"><div class="li"> Core <acronym title="Practical Extraction and Report Language">Perl</acronym> subroutines (split, pop, map, etc.)</div>
</li>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/customfunctions.html" class="wikilink1" title="documentation:1.4:customfunctions">Custom functions</a></div>
<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>
<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:1.4:extendedfunctions &crarr;" class="wikilink1">Informations about current request</a></div>
<li class="level1"><div class="li"> <a href="#request_informations" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">Informations about current request</a></div>
</li>
<li class="level1"><div class="li"> <a href="#extended_functions_list" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">Extended functions</a>:</div>
<li class="level1"><div class="li"> <a href="#extended_functions_list" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">Extended functions</a>:</div>
<ul>
<li class="level2"><div class="li"> <a href="#date" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">date</a></div>
<li class="level2"><div class="li"> <a href="#date" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">date</a></div>
</li>
<li class="level2"><div class="li"> <a href="#checklogonhours" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">checkLogonHours</a></div>
<li class="level2"><div class="li"> <a href="#checklogonhours" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">checkLogonHours</a></div>
</li>
<li class="level2"><div class="li"> <a href="#checkdate" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">checkDate</a></div>
<li class="level2"><div class="li"> <a href="#checkdate" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">checkDate</a></div>
</li>
<li class="level2"><div class="li"> <a href="#basic" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">basic</a></div>
<li class="level2"><div class="li"> <a href="#basic" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">basic</a></div>
</li>
<li class="level2"><div class="li"> <a href="#unicode2iso" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">unicode2iso</a></div>
<li class="level2"><div class="li"> <a href="#unicode2iso" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">unicode2iso</a></div>
</li>
<li class="level2"><div class="li"> <a href="#iso2unicode" title="documentation:1.4:extendedfunctions &crarr;" class="wikilink1">iso2unicode</a></div>
<li class="level2"><div class="li"> <a href="#iso2unicode" title="documentation:2.0:extendedfunctions &crarr;" class="wikilink1">iso2unicode</a></div>
</li>
</ul>
</li>
@ -154,7 +154,7 @@ For example, for a full access, excepted week-end:
</pre>
<p>
<p><div class="notetip">The <a href="../../documentation/1.4/authldap.html#schema_extension" class="wikilink1" title="documentation:1.4: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/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
</div></p>
</p>
@ -224,7 +224,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/1.4/authldap.html#schema_extension" class="wikilink1" title="documentation:1.4:authldap">LDAP schema extension</a> can be used to store these values
<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
</div></p>
</p>
@ -264,12 +264,12 @@ checkDate($ssoStartDate, $ssoEndDate)
<p>
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.4/safejail.html" class="wikilink1" title="documentation:1.4: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/2.0/safejail.html" class="wikilink1" title="documentation:2.0: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> <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> header used in <a href="../../documentation/1.4/applications/authbasic.html" class="wikilink1" title="documentation:1.4:applications:authbasic">HTTP Basic authentication scheme</a>. It will force conversion from UTF-8 to <acronym title="International Organization for Standardization">ISO</acronym>-8859-1 of user and password data.
This function builds the <code>Authorization</code> <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 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 <acronym title="International Organization for Standardization">ISO</acronym>-8859-1 of user and password data.
</p>
<p>
@ -298,7 +298,7 @@ basic($uid,$_password)
<p>
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.4/safejail.html" class="wikilink1" title="documentation:1.4: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/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail to use it.
</div></p>
</p>
@ -330,7 +330,7 @@ unicode2iso($name)
<p>
<p><div class="noteimportant">This function is not compliant with <a href="../../documentation/1.4/safejail.html" class="wikilink1" title="documentation:1.4: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/2.0/safejail.html" class="wikilink1" title="documentation:2.0:safejail">Safe jail</a>, you will need to disable the jail to use it.
</div></p>
</p>

@ -44,11 +44,11 @@ So you can configure it to authenticate users using a federation protocol and si
For example, a <acronym title="LemonLDAP::NG">LL::NG</acronym> server can be:
</p>
<ul>
<li class="level1"><div class="li"> A <a href="../../documentation/1.4/idpcas.html" class="wikilink1" title="documentation:1.4:idpcas">CAS server</a> with <a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML authentication</a></div>
<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>
<li class="level1"><div class="li"> An <a href="../../documentation/1.4/idpopenid.html" class="wikilink1" title="documentation:1.4:idpopenid">OpenID server</a> with <a href="../../documentation/1.4/authcas.html" class="wikilink1" title="documentation:1.4:authcas">CAS authentication</a></div>
<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>
<li class="level1"><div class="li"> An <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML server</a> with <a href="../../documentation/1.4/authopenid.html" class="wikilink1" title="documentation:1.4:authopenid">OpenID authentication</a></div>
<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>
<li class="level1"><div class="li"></div>
</li>
@ -59,9 +59,9 @@ For example, a <acronym title="LemonLDAP::NG">LL::NG</acronym> server can be:
See the following chapters:
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.4:start">Authentication protocols</a></div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#identity_provider" class="wikilink1" title="documentation:1.4:start">Identity provider</a></div>
<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>
</ul>

@ -34,7 +34,7 @@ This is the default configuration backend. Datas are stored as key/values (no-st
<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/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP configuration backend proxy</a></div>
<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>
<li class="level1"><div class="li"> any files sharing system (NFS, NAS, SAN,…)</div>
</li>

@ -27,7 +27,7 @@
<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/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4: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/2.0/soapsessionbackend.html" class="wikilink1" title="documentation:2.0:soapsessionbackend">SOAP proxy</a>.
</p>
</div>

@ -41,7 +41,7 @@ This kind of <acronym title="Single Sign On">SSO</acronym> mechanism is not clea
</p>
<p>
Please always try to find another solution to protect your application with <acronym title="LemonLDAP::NG">LL::NG</acronym>. At least, check if it is not a <a href="../../documentation/1.4/applications.html" class="wikilink1" title="documentation:1.4:applications">known application</a>, or <a href="../../documentation/1.4/selfmadeapplication.html" class="wikilink1" title="documentation:1.4:selfmadeapplication">try to adapt its source code</a>.
Please always try to find another solution to protect your application with <acronym title="LemonLDAP::NG">LL::NG</acronym>. 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>.
</div></p>
</p>
@ -56,7 +56,7 @@ POST data can be static values or computed from user&#039;s session.
<p>
<p><div class="notetip">
To post user&#039;s password, you must enable <a href="../../documentation/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4: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&#039;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.
</div></p>
</p>
@ -122,7 +122,7 @@ Then go in Manager, “Virtual Hosts” » <em>virtualhost</em> » “Form repla
</p>
<p>
<a href="/_detail/documentation/manager-formreplay-newurl.png?id=documentation%3A1.4%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%3A2.0%3Aformreplay" class="media" title="documentation:manager-formreplay-newurl.png"><img src="../../../media/documentation/manager-formreplay-newurl.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -147,7 +147,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%3A1.4%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%3A2.0%3Aformreplay" class="media" title="documentation:manager-formreplay-newdata.png"><img src="../../../media/documentation/manager-formreplay-newdata.png" class="mediacenter" alt="" /></a>
</p>
<p>

@ -56,7 +56,7 @@ This can be useful to allow an third party application to access a virtual host
<p>
Configure the virtual host like other <a href="../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a> but use AuthBasic Handler instead of default Handler.
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.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> basic.example.com
@ -89,7 +89,7 @@ If LemonLDAP::NG portal is protected by <acronym title="Secure Sockets Layer">SS
<p>
No parameters needed. But you have to allow sessions web services, see <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4:soapsessionbackend">SOAP sessions backend</a>.
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>.
</p>
</div>

@ -76,7 +76,7 @@ Sometimes, <acronym title="Hypertext Preprocessor">PHP</acronym> applications al
<p>
Of course, you need to <a href="../../documentation/1.4/passwordstore.html" class="wikilink1" title="documentation:1.4:passwordstore">store password in session</a> to fill <acronym title="Hypertext Preprocessor">PHP</acronym>_AUTH_PW.
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 <acronym title="Hypertext Preprocessor">PHP</acronym>_AUTH_PW.
</div></p>

@ -42,7 +42,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%3A1.4%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%3A2.0%3Ahighavailability" class="media" title="documentation:ha-apache.png"><img src="../../../media/documentation/ha-apache.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -50,7 +50,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%3A1.4%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%3A2.0%3Ahighavailability" class="media" title="documentation:ha-sessions-configuration.png"><img src="../../../media/documentation/ha-sessions-configuration.png" class="mediacenter" alt="" /></a>
</p>
</div>

@ -35,7 +35,7 @@
<acronym title="LemonLDAP::NG">LL::NG</acronym> can act as an <acronym title="Central Authentication Service">CAS</acronym> server, that can allow to federate <acronym title="LemonLDAP::NG">LL::NG</acronym> with:
</p>
<ul>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/1.4/authcas.html" class="wikilink1" title="documentation:1.4:authcas">CAS authentication</a></div>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/2.0/authcas.html" class="wikilink1" title="documentation:2.0:authcas">CAS authentication</a></div>
</li>
<li class="level1"><div class="li"> Any <acronym title="Central Authentication Service">CAS</acronym> consumer</div>
</li>
@ -58,7 +58,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/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4: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/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0: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>
@ -82,7 +82,7 @@ $authenticationLevel &gt; 2
<p>
<p><div class="noteimportant">
Apache rewrite rules must have been activated in <a href="../../documentation/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4:configlocation">Apache portal configuration</a>:
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>:
</p>
<pre class="code file apache"> &lt;<span class="kw3">IfModule</span> mod_rewrite.c&gt;
@ -112,7 +112,7 @@ Then go in <code>Options</code> to define:
</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong><acronym title="Central Authentication Service">CAS</acronym> session module name and options</strong>: choose a specific module if you do not want to mix <acronym title="Central Authentication Service">CAS</acronym> sessions and normal sessions (see <a href="../../documentation/1.4/samlservice.html#saml_sessions_module_name_and_options" class="wikilink1" title="documentation:1.4:samlservice">why</a>).</div>
<li class="level1"><div class="li"> <strong><acronym title="Central Authentication Service">CAS</acronym> session module name and options</strong>: choose a specific module if you do not want to mix <acronym title="Central Authentication Service">CAS</acronym> 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>
</ul>

@ -35,7 +35,7 @@
<acronym title="LemonLDAP::NG">LL::NG</acronym> can act as an OpenID 2.0 Server, that can allow to federate <acronym title="LemonLDAP::NG">LL::NG</acronym> with:
</p>
<ul>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/1.4/authopenid.html" class="wikilink1" title="documentation:1.4:authopenid">OpenID authentication</a></div>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/2.0/authopenid.html" class="wikilink1" title="documentation:2.0:authopenid">OpenID authentication</a></div>
</li>
<li class="level1"><div class="li"> Any OpenID consumer</div>
</li>
@ -52,7 +52,7 @@ When <acronym title="LemonLDAP::NG">LL::NG</acronym> is configured as OpenID ide
<ul>
<li class="level1"><div class="li"> [PORTAL] is the portal <acronym title="Uniform Resource Locator">URL</acronym></div>
</li>
<li class="level1"><div class="li"> [login] is the user login (or any other session information, <span class="curid"><a href="../../documentation/1.4/idpopenid.html#configuration" class="wikilink1" title="documentation:1.4: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/2.0/idpopenid.html#configuration" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>)</div>
</li>
</ul>
@ -77,7 +77,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/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4: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/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0: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>
@ -101,7 +101,7 @@ $authenticationLevel &gt; 2
<p>
<p><div class="noteimportant">
Apache rewrite rules must have been activated in <a href="../../documentation/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4:configlocation">Apache portal configuration</a>:
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>:
</p>
<pre class="code file apache"> &lt;<span class="kw3">IfModule</span> mod_rewrite.c&gt;
@ -119,13 +119,13 @@ Apache rewrite rules must have been activated in <a href="../../documentation/1.
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/1.4/idpopenid.html#security" class="wikilink1" title="documentation:1.4: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/2.0/idpopenid.html#security" class="wikilink1" title="documentation:2.0: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/1.4/idpopenid.html#security" class="wikilink1" title="documentation:1.4: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/2.0/idpopenid.html#security" class="wikilink1" title="documentation:2.0: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/1.4/idpopenid.html#shared_attributes_sreg" class="wikilink1" title="documentation:1.4: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/2.0/idpopenid.html#shared_attributes_sreg" class="wikilink1" title="documentation:2.0:idpopenid">see below</a></span>).</div>
</li>
</ul>
@ -188,7 +188,7 @@ Each SREG attribute will be associated to a user session key. A session key can
<p>
<p><div class="noteimportant">Note that <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML</a> protocol is more secured than OpenID, so when your partners are known, prefer <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML</a>.
<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>.
</div></p>
</p>

@ -35,17 +35,17 @@
<acronym title="LemonLDAP::NG">LL::NG</acronym> can act as an <acronym title="Security Assertion Markup Language">SAML</acronym> 2.0 Identity Provider, that can allow to federate <acronym title="LemonLDAP::NG">LL::NG</acronym> with:
</p>
<ul>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML authentication</a></div>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML authentication</a></div>
</li>
<li class="level1"><div class="li"> Any <acronym title="Security Assertion Markup Language">SAML</acronym> Service Provider, for example:</div>
</li>
</ul>
<div class="plugin_include_content" id="plugin_include__documentation:1.4:applications">
<div class="plugin_include_content" id="plugin_include__documentation:2.0:applications">
<div class="level2">
<p>
<p><div class="noteclassic">This requires to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <span class="curid"><a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML Identity Provider</a></span>.
<p><div class="noteclassic">This requires to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as an <span class="curid"><a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML Identity Provider</a></span>.
</div></p>
</p>
@ -54,7 +54,7 @@
<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>
</tr>
<tr class="row1 rowodd">
<td class="col0 centeralign"> <a href="../../documentation/1.4/applications/googleapps.html" class="media" title="documentation:1.4: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/1.4/applications/cornerstone.html" class="media" title="documentation:1.4:applications:cornerstone"><img src="../../../media/applications/csod_logo.png" class="media" alt="" /></a> </td><td class="col4 leftalign"> <a href="../../documentation/1.4/applications/salesforce.html" class="media" title="documentation:1.4:applications:salesforce"><img src="../../../media/applications/salesforce-logo.jpg" class="medialeft" align="left" alt="" /></a> </td>
<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>
</tr>
</table>
@ -74,7 +74,7 @@
<p>
See <a href="../../documentation/1.4/samlservice.html" class="wikilink1" title="documentation:1.4:samlservice">SAML service</a> configuration chapter.
See <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0:samlservice">SAML service</a> configuration chapter.
</p>
</div>
@ -89,7 +89,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 <acronym title="Security Assertion Markup Language">SAML</acronym> end points suffix in <a href="../../documentation/1.4/samlservice.html" class="wikilink1" title="documentation:1.4:samlservice">SAML service configuration</a>.</div>
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/saml/</code> unless you have change <acronym title="Security Assertion Markup Language">SAML</acronym> end points suffix in <a href="../../documentation/2.0/samlservice.html" class="wikilink1" title="documentation:2.0: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>
@ -136,7 +136,7 @@ In the Manager, select node <acronym title="Security Assertion Markup Language">
</p>
<p>
<a href="/_detail/documentation/manager-saml-sp-new.png?id=documentation%3A1.4%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%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>
</p>
<p>
@ -196,7 +196,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/1.4/samlservice.html" class="wikilink1" title="documentation:1.4: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/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>
<li class="level1"><div class="li"> <strong>One Time Use</strong>: set the OneTimeUse flag in authentication response (<code>&lt;Condtions&gt;</code>).</div>
</li>
@ -228,7 +228,7 @@ For each attribute, you can set:
<p>
These options override service signature options (see <a href="../../documentation/1.4/samlservice.html#general_options" class="wikilink1" title="documentation:1.4:samlservice">SAML service configuration</a>).
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>).
</p>
<ul>

@ -154,7 +154,7 @@ aptitude install lemonldap-ng
<p>
Before installing the packages, install <a href="../../documentation/1.4/prereq.html" class="wikilink1" title="documentation:1.4:prereq">dependencies</a>.
Before installing the packages, install <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">dependencies</a>.
</p>
<p>
@ -233,7 +233,7 @@ To allow the manager to reload the configuration, register the reload virtual ho
<p>
If you upgraded <acronym title="LemonLDAP::NG">LL::NG</acronym>, check all <a href="../../documentation/1.4/upgrade.html" class="wikilink1" title="documentation:1.4:upgrade">upgrade notes</a>.
If you upgraded <acronym title="LemonLDAP::NG">LL::NG</acronym>, check all <a href="../../documentation/2.0/upgrade.html" class="wikilink1" title="documentation:2.0:upgrade">upgrade notes</a>.
</p>
<p>
@ -244,7 +244,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">&#123;</span> 'Menu' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'Example' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'test1' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Application Test <span class="nu0">1</span>', uri <span class="sy0">=</span>&gt; 'http://test1.example.com/', description <span class="sy0">=</span>&gt; 'A simple application displaying authenticated user', logo <span class="sy0">=</span>&gt; 'wheels.png', display <span class="sy0">=</span>&gt; 'auto', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'test2' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Application Test <span class="nu0">2</span>', uri <span class="sy0">=</span>&gt; 'http://test2.example.com/', description <span class="sy0">=</span>&gt; 'The same simple application displaying authenticated user', logo <span class="sy0">=</span>&gt; 'wheels.png', display <span class="sy0">=</span>&gt; 'auto', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'Administration' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'manager' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'WebSSO Manager', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/', description <span class="sy0">=</span>&gt; 'Configure LemonLDAP::NG WebSSO', logo <span class="sy0">=</span>&gt; 'tools.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'sessions' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Sessions explorer', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/sessions.pl', description <span class="sy0">=</span>&gt; 'Explore WebSSO sessions', logo <span class="sy0">=</span>&gt; 'tools.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'Documentation' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'localdoc' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Local documentation', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/doc/', description <span class="sy0">=</span>&gt; 'Documentation supplied with LemonLDAP::NG', logo <span class="sy0">=</span>&gt; 'docs.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'officialwebsite' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Offical Website', uri <span class="sy0">=</span>&gt; 'http://wiki.lemonldap.objectweb.org/xwiki/bin/view/NG/Presentation', description <span class="sy0">=</span>&gt; 'Official LemonLDAP::NG Website', logo <span class="sy0">=</span>&gt; 'web.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span></span></pre>
<p>
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4: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/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>.
</div></p>
</p>
@ -272,7 +272,7 @@ For tests with <code>example.com</code>, launch the following :
</p>
<p>
Follow the <a href="../../documentation/1.4/start.html#configuration" class="wikilink1" title="documentation:1.4:start">next steps</a>
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>
</p>
</div>

@ -65,7 +65,7 @@ This schema shows the dependencies between modules:
</p>
<p>
<a href="/_detail/documentation/lemonldap-ng-packages.png?id=documentation%3A1.4%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%3A2.0%3Ainstallrpm" class="media" title="documentation:lemonldap-ng-packages.png"><img src="../../../media/documentation/lemonldap-ng-packages.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -129,7 +129,7 @@ yum update
<p>
<p><div class="notewarning">
You must also install the EPEL repository for non-core dependencies. See <a href="../../documentation/1.4/prereq.html#yum" class="wikilink1" title="documentation:1.4:prereq">prerequisites and dependencies</a> chapter for more.
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.
</div></p>
</p>
@ -200,7 +200,7 @@ yum localinstall lemonldap-ng-* perl-Lemonldap-NG-*
<p>
Before installing the packages, install all <a href="../../documentation/1.4/prereq.html" class="wikilink1" title="documentation:1.4:prereq">dependencies</a>.
Before installing the packages, install all <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">dependencies</a>.
</p>
<p>
@ -321,7 +321,7 @@ To allow the manager to reload the configuration, register the reload virtual ho
<p>
If you upgraded <acronym title="LemonLDAP::NG">LL::NG</acronym>, check all <a href="../../documentation/1.4/upgrade.html" class="wikilink1" title="documentation:1.4:upgrade">upgrade notes</a>.
If you upgraded <acronym title="LemonLDAP::NG">LL::NG</acronym>, check all <a href="../../documentation/2.0/upgrade.html" class="wikilink1" title="documentation:2.0:upgrade">upgrade notes</a>.
</p>
<p>
@ -344,7 +344,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">&#123;</span> 'Menu' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'Example' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'test1' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Application Test <span class="nu0">1</span>', uri <span class="sy0">=</span>&gt; 'http://test1.example.com/', description <span class="sy0">=</span>&gt; 'A simple application displaying authenticated user', logo <span class="sy0">=</span>&gt; 'wheels.png', display <span class="sy0">=</span>&gt; 'auto', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'test2' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Application Test <span class="nu0">2</span>', uri <span class="sy0">=</span>&gt; 'http://test2.example.com/', description <span class="sy0">=</span>&gt; 'The same simple application displaying authenticated user', logo <span class="sy0">=</span>&gt; 'wheels.png', display <span class="sy0">=</span>&gt; 'auto', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'Administration' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'manager' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'WebSSO Manager', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/', description <span class="sy0">=</span>&gt; 'Configure LemonLDAP::NG WebSSO', logo <span class="sy0">=</span>&gt; 'tools.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'sessions' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Sessions explorer', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/sessions.pl', description <span class="sy0">=</span>&gt; 'Explore WebSSO sessions', logo <span class="sy0">=</span>&gt; 'tools.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'Documentation' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'category', 'localdoc' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Local documentation', uri <span class="sy0">=</span>&gt; 'http://manager.example.com/doc/', description <span class="sy0">=</span>&gt; 'Documentation supplied with LemonLDAP::NG', logo <span class="sy0">=</span>&gt; 'docs.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>,'officialwebsite' <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> type <span class="sy0">=</span>&gt; 'application', options <span class="sy0">=</span>&gt; <span class="br0">&#123;</span> name <span class="sy0">=</span>&gt; 'Offical Website', uri <span class="sy0">=</span>&gt; 'http://wiki.lemonldap.objectweb.org/xwiki/bin/view/NG/Presentation', description <span class="sy0">=</span>&gt; 'Official LemonLDAP::NG Website', logo <span class="sy0">=</span>&gt; 'web.png', display <span class="sy0">=</span>&gt; 'on', <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span>, <span class="br0">&#125;</span></span></pre>
<p>
<p><div class="noteimportant">You should now use the Manager to configure all <a href="../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4: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/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>.
</div></p>
</p>
@ -372,7 +372,7 @@ For tests with <code>example.com</code>, launch the following :
</p>
<p>
Follow the <a href="../../documentation/1.4/start.html#configuration" class="wikilink1" title="documentation:1.4:start">next steps</a>
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>
</p>
</div>

@ -91,7 +91,7 @@ tar zxvf lemonldap-ng-*.tar.gz
<p>
First check and install the <a href="../../documentation/1.4/prereq.html" class="wikilink1" title="documentation:1.4:prereq">prerequisites</a>.
First check and install the <a href="../../documentation/2.0/prereq.html" class="wikilink1" title="documentation:2.0:prereq">prerequisites</a>.
</p>
<p>
@ -230,7 +230,7 @@ make ubuntu-install
<p>
See also <a href="../../documentation/1.4/installdeb.html" class="wikilink1" title="documentation:1.4:installdeb">Debian/Ubuntu installation documentation</a>.
See also <a href="../../documentation/2.0/installdeb.html" class="wikilink1" title="documentation:2.0:installdeb">Debian/Ubuntu installation documentation</a>.
</div></p>
</p>
@ -324,7 +324,7 @@ For tests with the configured domain, launch the following :
</p>
<p>
Follow the <a href="../../documentation/1.4/start.html#configuration" class="wikilink1" title="documentation:1.4:start">next steps</a>.
Follow the <a href="../../documentation/2.0/start.html#configuration" class="wikilink1" title="documentation:2.0:start">next steps</a>.
</p>

@ -41,7 +41,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 <acronym title="Secure Sockets Layer">SSL</acronym> hardware equipments</div>
</li>
<li class="level1"><div class="li"> It is compliant with the <a href="../../documentation/1.4/formreplay.html" class="wikilink1" title="documentation:1.4:formreplay">form replay</a> feature</div>
<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>
</ul>

@ -27,14 +27,14 @@
<p>
This works like <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File backend</a>, except that data are serialized in JSON.
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.
</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/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP configuration backend proxy</a></div>
<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>
<li class="level1"><div class="li"> any files sharing system (NFS, NAS, SAN,…)</div>
</li>

@ -36,7 +36,7 @@ You can choose to store LemonLDAP::NG configuration in an <acronym title="Lightw
</p>
<p>
<a href="/_detail/documentation/configuration-ldap.png?id=documentation%3A1.4%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%3A2.0%3Aldapconfbackend" class="media" title="documentation:configuration-ldap.png"><img src="../../../media/documentation/configuration-ldap.png" class="mediacenter" alt="" /></a>
</p>
<p>

@ -40,9 +40,9 @@
Steps:
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">Prepare the LDAP server and the LL::NG configuration file</a></div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/changeconfbackend.html" class="wikilink1" title="documentation:1.4:changeconfbackend">Convert existing configuration</a></div>
<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>
<li class="level1"><div class="li"> Restart all your Apache servers</div>
</li>
@ -58,7 +58,7 @@ Steps:
Steps:
</p>
<ul>
<li class="level1"><div class="li"> Follow <a href="../../documentation/1.4/ldapsessionbackend.html" class="wikilink1" title="documentation:1.4:ldapsessionbackend">LDAP session backend</a> doc</div>
<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>
</ul>

@ -58,11 +58,11 @@ By default, login time and <acronym title="Internet Protocol">IP</acronym> addre
</p>
<p>
To allow the Login History tab in Menu, configure it in <code>General Parameters</code> &gt; <code>Portal</code> &gt; <code>Menu</code> &gt; <code>Modules</code> (see <a href="../../documentation/1.4/portalmenu.html#menu_modules" class="wikilink1" title="documentation:1.4:portalmenu">portal menu configuration</a>).
To allow the Login History tab in Menu, configure it in <code>General Parameters</code> &gt; <code>Portal</code> &gt; <code>Menu</code> &gt; <code>Modules</code> (see <a href="../../documentation/2.0/portalmenu.html#menu_modules" class="wikilink1" title="documentation:2.0: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/1.4/portalcustom.html#other_parameters" class="wikilink1" title="documentation:1.4: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/2.0/portalcustom.html#other_parameters" class="wikilink1" title="documentation:2.0:portalcustom">portal customization</a>).
</p>

@ -32,7 +32,7 @@
<p>
Even if LL:NG can catch logout <acronym title="Uniform Resource Locator">URL</acronym> trough <a href="../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4: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 <acronym title="Uniform Resource Locator">URL</acronym> 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.
</p>
<p>

@ -92,7 +92,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/1.4/configvhost.html#lemonldapng_configuration" class="wikilink1" title="documentation:1.4: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/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.
</p>
<p>
@ -136,7 +136,7 @@ Restart Apache and try to log on Manager. You should be redirected to <acronym t
</p>
<p>
You can then add the Manager as <a href="../../documentation/1.4/portalmenu.html#categories_and_applications" class="wikilink1" title="documentation:1.4:portalmenu">an application in the menu</a>.
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>.
</p>
<p>

@ -40,7 +40,7 @@
<p>
To keep Memcached performance level and <acronym title="LemonLDAP::NG">LL::NG</acronym> 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.4/nosqlsessionbackend.html" class="wikilink1" title="documentation:1.4:nosqlsessionbackend">NoSQL session backend</a>.
To keep Memcached performance level and <acronym title="LemonLDAP::NG">LL::NG</acronym> 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>.
</div></p>
</p>

@ -27,7 +27,7 @@
<p>
<a href="../../documentation/1.4/status.html" class="wikilink1" title="documentation:1.4: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/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.
</p>
<p>

@ -40,9 +40,9 @@
Steps:
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">Prepare the database and the LL::NG configuration file</a></div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/changeconfbackend.html" class="wikilink1" title="documentation:1.4:changeconfbackend">Convert existing configuration</a></div>
<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>
<li class="level1"><div class="li"> Restart all your Apache servers</div>
</li>
@ -60,9 +60,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/1.4/browseablesessionbackend.html" class="wikilink1" title="documentation:1.4:browseablesessionbackend">Using Apache::Session::Browseable::MySQL</a> (recommended for best performances)</div>
<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>
<li class="level2"><div class="li"> <a href="../../documentation/1.4/sqlsessionbackend.html" class="wikilink1" title="documentation:1.4:sqlsessionbackend">Using Apache::Session::MySQL</a> <em>(if you choose this option, then read <a href="../../documentation/1.4/performances.html#apachesession_performances" class="wikilink1" title="documentation:1.4:performances">how to increase MySQL performances</a>)</em></div>
<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>
</ul>
</li>

@ -63,7 +63,7 @@ In the manager: set <a href="http://search.cpan.org/perldoc?Apache::Session::Red
<p>
Restrict network access to the redis server. For remote servers, you can use <a href="../../documentation/1.4/soapsessionbackend.html" class="wikilink1" title="documentation:1.4: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/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
</p>

@ -82,7 +82,7 @@ You can change default parameters using the “notificationStorage” and “not
<p>
Parameters for File backend are the same as <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File configuration backend</a>.
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>.
</p>
<p>
@ -122,7 +122,7 @@ To summary available options:
<p>
Parameters for <acronym title="Database Interface">DBI</acronym> backend are the same as <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">DBI configuration backend</a>.
Parameters for <acronym title="Database Interface">DBI</acronym> backend are the same as <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">DBI configuration backend</a>.
</p>
<p>
@ -166,7 +166,7 @@ To summary available options:
<p>
Parameters for <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> backend are the same as <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP configuration backend</a>.
Parameters for <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> backend are the same as <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP configuration backend</a>.
</p>
<p>
@ -310,7 +310,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%3A1.4%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%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>
</p>
<p>
@ -417,7 +417,7 @@ You&#039;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%3A1.4%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%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>
</p>
<p>

@ -29,7 +29,7 @@
<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 <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to override configuration parameters (see <a href="../../documentation/1.4/configlocation.html" class="wikilink1" title="documentation:1.4:configlocation">configuration location</a>).
The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or in <acronym title="Practical Extraction and Report Language">Perl</acronym> scripts to override configuration parameters (see <a href="../../documentation/2.0/configlocation.html" class="wikilink1" title="documentation:2.0:configlocation">configuration location</a>).
</div></p>
</p>
@ -601,7 +601,7 @@ The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or
<th class="col0 centeralign"> Full name </th><th class="col1 centeralign"> Key name </th><th class="col2 centeralign"> Configuration backend </th>
</tr>
<tr class="row1 rowodd">
<td class="col0"> <acronym title="Database Interface">DBI</acronym> connection string </td><td class="col1"> dbiChain </td><td class="col2" rowspan="4"> <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">CDBI / RDBI</a> </td>
<td class="col0"> <acronym title="Database Interface">DBI</acronym> 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>
</tr>
<tr class="row2 roweven">
<td class="col0"> <acronym title="Database Interface">DBI</acronym> user </td><td class="col1"> dbiUser </td>
@ -613,10 +613,10 @@ The attribute key name can be used directly in <code>lemonldap-ng.ini</code> or
<td class="col0"> <acronym title="Database Interface">DBI</acronym> 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/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File</a> </td>
<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>
</tr>
<tr class="row6 roweven">
<td class="col0"> <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> server </td><td class="col1"> ldapServer </td><td class="col2" rowspan="7"> <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP</a> </td>
<td class="col0"> <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> 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>
</tr>
<tr class="row7 rowodd">
<td class="col0"> <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> port </td><td class="col1"> ldapPort </td>
@ -637,7 +637,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"> <acronym title="Simple Object Access Protocol">SOAP</acronym> server location (<acronym title="Uniform Resource Locator">URL</acronym>) </td><td class="col1"> proxy </td><td class="col2" rowspan="2"> <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP</a> </td>
<td class="col0"> <acronym title="Simple Object Access Protocol">SOAP</acronym> server location (<acronym title="Uniform Resource Locator">URL</acronym>) </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>
</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>

@ -45,7 +45,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/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP</a>, <a href="../../documentation/1.4/authdbi.html" class="wikilink1" title="documentation:1.4: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/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>
</ul>

@ -67,7 +67,7 @@ Handlers check rights and calculate headers for each <acronym title="Hyper Text
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/1.4/exportedvars.html" class="wikilink1" title="documentation:1.4: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/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>
<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>

@ -34,33 +34,33 @@ The portal is the main component of <acronym title="LemonLDAP::NG">LL::NG</acron
<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/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP</a>, <a href="../../documentation/1.4/authdbi.html" class="wikilink1" title="documentation:1.4:authdbi">SQL</a>, …)</div>
<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>
<li class="level3"><div class="li"> using Apache authentication system (used for <a href="../../documentation/1.4/authssl.html" class="wikilink1" title="documentation:1.4:authssl">SSL</a>, <a href="../../documentation/1.4/authapache.html" class="wikilink1" title="documentation:1.4:authapache">Kerberos</a>, <a href="../../documentation/1.4/authapache.html" class="wikilink1" title="documentation:1.4:authapache">HTTP basic authentication</a>, …)</div>
<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>
<li class="level3"><div class="li"> using external identity provider (<a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML</a>, <a href="../../documentation/1.4/authopenid.html" class="wikilink1" title="documentation:1.4:authopenid">OpenID</a>, <a href="../../documentation/1.4/authcas.html" class="wikilink1" title="documentation:1.4:authcas">CAS</a>, <a href="../../documentation/1.4/authtwitter.html" class="wikilink1" title="documentation:1.4:authtwitter">Twitter</a>, other <acronym title="LemonLDAP::NG">LL::NG</acronym> system, …)</div>
<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 <acronym title="LemonLDAP::NG">LL::NG</acronym> system, …)</div>
</li>
<li class="level3"><div class="li"> all together (based on user <a href="../../documentation/1.4/authchoice.html" class="wikilink1" title="documentation:1.4:authchoice">choice</a>, <a href="../../documentation/1.4/authmulti.html" class="wikilink1" title="documentation:1.4:authmulti">rules</a>, …)</div>
<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>
</ul>
</li>
<li class="level2"><div class="li"> <a href="../../documentation/1.4/soapservices.html" class="wikilink1" title="documentation:1.4:soapservices">SOAP based</a> for client-server software, specific development, …</div>
<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>
</ul>
</li>
<li class="level1"><div class="li"> <strong>Identity provider</strong>: <acronym title="LemonLDAP::NG">LL::NG</acronym> is able to provide identity service using:</div>
<ul>
<li class="level2"><div class="li"> <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML</a></div>
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML</a></div>
</li>
<li class="level2"><div class="li"> <a href="../../documentation/1.4/idpopenid.html" class="wikilink1" title="documentation:1.4:idpopenid">OpenID</a></div>
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpopenid.html" class="wikilink1" title="documentation:2.0:idpopenid">OpenID</a></div>
</li>
<li class="level2"><div class="li"> <a href="../../documentation/1.4/idpcas.html" class="wikilink1" title="documentation:1.4:idpcas">CAS</a></div>
<li class="level2"><div class="li"> <a href="../../documentation/2.0/idpcas.html" class="wikilink1" title="documentation:2.0:idpcas">CAS</a></div>
</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.4/federationproxy.html" class="wikilink1" title="documentation:1.4:federationproxy">Identity provider proxy</a></strong>: <acronym title="LemonLDAP::NG">LL::NG</acronym> can be used as proxy translator between systems talking <acronym title="Security Assertion Markup Language">SAML</acronym>, OpenID, <acronym title="Central Authentication Service">CAS</acronym>, …</div>
<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>: <acronym title="LemonLDAP::NG">LL::NG</acronym> can be used as proxy translator between systems talking <acronym title="Security Assertion Markup Language">SAML</acronym>, OpenID, <acronym title="Central Authentication Service">CAS</acronym>, …</div>
</li>
<li class="level1"><div class="li"> <strong>Internal <acronym title="Simple Object Access Protocol">SOAP</acronym> server</strong> used by <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP configuration backend</a> and usable for specific development (see <a href="../../documentation/1.4/soapservices.html" class="wikilink1" title="documentation:1.4:soapservices">SOAP services</a> for more)</div>
<li class="level1"><div class="li"> <strong>Internal <acronym title="Simple Object Access Protocol">SOAP</acronym> 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>
<li class="level1"><div class="li"> Interactive <strong>management of user passwords</strong>:</div>
<ul>
@ -72,9 +72,9 @@ The portal is the main component of <acronym title="LemonLDAP::NG">LL::NG</acron
</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.4/portalmenu.html" class="wikilink1" title="documentation:1.4:portalmenu">Application menu</a></strong>: display authorized applications in categories</div>
<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>
<li class="level1"><div class="li"> <strong><a href="../../documentation/1.4/notifications.html" class="wikilink1" title="documentation:1.4: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/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>
</ul>
@ -88,13 +88,13 @@ The portal is the main component of <acronym title="LemonLDAP::NG">LL::NG</acron
<acronym title="LemonLDAP::NG">LL::NG</acronym> portal is a modular component. It needs 4 modules to work:
</p>
<ul>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.4:start">Authentication</a>: how check user credentials</div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.4:start">User database</a>: where collect user information</div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#authentication_users_and_password_databases" class="wikilink1" title="documentation:1.4:start">Password database</a>: where change password</div>
<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>
<li class="level1"><div class="li"> <a href="../../documentation/1.4/start.html#identity_provider" class="wikilink1" title="documentation:1.4:start">Identity provider</a>: how forward user identity</div>
<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>
</ul>
@ -121,7 +121,7 @@ The portal is the main component of <acronym title="LemonLDAP::NG">LL::NG</acron
</li>
<li class="level1"><div class="li"> Provides identity if asked</div>
</li>
<li class="level1"><div class="li"> Build <a href="../../documentation/1.4/ssocookie.html" class="wikilink1" title="documentation:1.4:ssocookie">cookie(s)</a></div>
<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>
<li class="level1"><div class="li"> Redirect user to the asked <acronym title="Uniform Resource Locator">URL</acronym> or display menu</div>
</li>

@ -67,7 +67,7 @@ You can change the default skin in Manager: <code>General Parameters</code> &gt;
</p>
<p>
<a href="/_detail/documentation/manager-portalskin.png?id=documentation%3A1.4%3Aportalcustom" class="media" title="documentation:manager-portalskin.png"><img src="../../../media/documentation/manager-portalskin.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-portalskin.png?id=documentation%3A2.0%3Aportalcustom" class="media" title="documentation:manager-portalskin.png"><img src="../../../media/documentation/manager-portalskin.png" class="mediacenter" alt="" /></a>
</p>
</div>
@ -222,9 +222,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/1.4/resetpassword.html" class="wikilink1" title="documentation:1.4: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/2.0/resetpassword.html" class="wikilink1" title="documentation:2.0: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/1.4/register.html" class="wikilink1" title="documentation:1.4: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/2.0/register.html" class="wikilink1" title="documentation:2.0:register">register page</a> (for password based authentication backends)</div>
</li>
</ul>

@ -69,7 +69,7 @@ You can use <code>0</code> or <code>1</code> to disable/enable the module, or us
<p>
<a href="../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4: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/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>).
</p>
<p>
@ -92,7 +92,7 @@ Application parameters:
</p>
<p>
<a href="/_detail/documentation/manager-menu-application.png?id=documentation%3A1.4%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%3A2.0%3Aportalmenu" class="media" title="documentation:manager-menu-application.png"><img src="../../../media/documentation/manager-menu-application.png" class="mediacenter" alt="" /></a>
</p>
<ul>
@ -125,7 +125,7 @@ Application parameters:
</p>
<p>
<a href="/_detail/documentation/manager-menu-application-logo.png?id=documentation%3A1.4%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%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>
</p>
<p>

@ -36,7 +36,7 @@
</p>
<p>
LemonLDAP::NG allows to use this model. You should use an <a href="../../documentation/1.4/authldap.html#schema_extension" class="wikilink1" title="documentation:1.4: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/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.
</p>
</div>
@ -86,7 +86,7 @@ Now imagine the following DIT:
</p>
<p>
<a href="/_detail/documentation/dia_dit_roles.png?id=documentation%3A1.4%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%3A2.0%3Arbac" class="media" title="documentation:dia_dit_roles.png"><img src="../../../media/documentation/dia_dit_roles.png" class="mediacenter" alt="" /></a>
</p>
<p>

@ -53,7 +53,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/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">virtual host management</a>.
<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>.
</div></p>
</p>

@ -54,7 +54,7 @@ This feature is a page that allows a user to create an account. The steps are th
<p>
You can enable the “Create your account” button in <a href="../../documentation/1.4/portalcustom.html" class="wikilink1" title="documentation:1.4:portalcustom">portal customization parameters</a>.
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>.
</p>
<p>

@ -44,7 +44,7 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step1.png?id=documentation%3A1.4%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%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>
</p>
<ul>
<li class="level1"><div class="li"> User enters his email (or another information) in the password reset form</div>
@ -54,7 +54,7 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A1.4%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%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>
</p>
<ul>
<li class="level1"><div class="li"> A mail with a token is sent to user</div>
@ -62,7 +62,7 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step3.png?id=documentation%3A1.4%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%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>
</p>
<ul>
<li class="level1"><div class="li"> The user click on the link in the mail</div>
@ -70,7 +70,7 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step4.png?id=documentation%3A1.4%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%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>
</p>
<ul>
<li class="level1"><div class="li"> <acronym title="LemonLDAP::NG">LL::NG</acronym> validate the token and propose a password change form</div>
@ -80,7 +80,7 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step2.png?id=documentation%3A1.4%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%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>
</p>
<ul>
<li class="level1"><div class="li"> The new password is sent to user</div>
@ -88,11 +88,11 @@ Kinematics:
</ul>
<p>
<a href="/_detail/screenshots/1.1/mailreset/mailreset_step5.png?id=documentation%3A1.4%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%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>
</p>
<p>
<p><div class="notetip">If <a href="../../documentation/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP backend</a> is used, and <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> password policy is enabled, the &#039;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.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">LDAP configuration</a>.
<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 <acronym title="Lightweight Directory Access Protocol">LDAP</acronym> password policy is enabled, the &#039;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>.
</div></p>
</p>
@ -108,7 +108,7 @@ Kinematics:
<p>
The reset password link must be activated, see <a href="../../documentation/1.4/portalcustom.html#other_parameters" class="wikilink1" title="documentation:1.4:portalcustom">portal customization</a>.
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>.
</p>
<p>

@ -71,7 +71,7 @@ More information about Safe on <a href="http://search.cpan.org/search?query=Safe
<p>
Safe can be very annoying when we use <a href="../../documentation/1.4/extendedfunctions.html" class="wikilink1" title="documentation:1.4:extendedfunctions">extended functions</a> or <a href="../../documentation/1.4/customfunctions.html" class="wikilink1" title="documentation:1.4:customfunctions">custom functions</a>. In this case, you might want to disabling it.
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.
</p>
<p>

@ -27,7 +27,7 @@
<p>
<p><div class="noteclassic"><acronym title="Security Assertion Markup Language">SAML</acronym> service configuration is a common step to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as <a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML SP</a> or <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML IDP</a>.
<p><div class="noteclassic"><acronym title="Security Assertion Markup Language">SAML</acronym> service configuration is a common step to configure <acronym title="LemonLDAP::NG">LL::NG</acronym> as <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML SP</a> or <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML IDP</a>.
</div></p>
</p>
@ -67,7 +67,7 @@ This documentation explains how configure <acronym title="Security Assertion Mar
<p>
<a href="/_detail/documentation/lasso.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:lasso.png"><img src="../../../media/documentation/lasso.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/lasso.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:lasso.png"><img src="../../../media/documentation/lasso.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -85,10 +85,10 @@ There are packages available here: <a href="http://deb.entrouvert.org/" class="u
</p>
<p>
You will only need to install liblasso3-perl package:
You will only need to install liblasso-perl package:
</p>
<pre class="code">
sudo apt-get install liblasso3-perl
sudo apt-get install liblasso-perl
</pre>
</div>
@ -98,18 +98,20 @@ sudo apt-get install liblasso3-perl
<p>
RPMs are available at
<a href="http://repo.cyrus-project.org/centos$releasever-$basearch/RPMS.cyrus-extras/" class="urlextern" title="http://repo.cyrus-project.org/centos$releasever-$basearch/RPMS.cyrus-extras/" rel="nofollow">http://repo.cyrus-project.org/centos$releasever-$basearch/RPMS.cyrus-extras/</a>
RPMs are available in <acronym title="LemonLDAP::NG">LL::NG</acronym> RPM repository (see <a href="../../documentation/2.0/installrpm.html#yum_repository" class="wikilink1" title="documentation:2.0:installrpm">yum_repository</a>)
</p>
<p>
<p><div class="notetip">Fill $releasever and $basearch with the correct values to get packages for your environment, for example <a href="http://repo.cyrus-project.org/centos5-i386/RPMS.cyrus-extras/" class="urlextern" title="http://repo.cyrus-project.org/centos5-i386/RPMS.cyrus-extras/" rel="nofollow">http://repo.cyrus-project.org/centos5-i386/RPMS.cyrus-extras/</a>
Then install lasso and lasso-perl packages:
</div></p>
</p>
<pre class="code">
yum install lasso lasso-perl
</pre>
<p>
Then install lasso and lasso-perl packages.
<p><div class="noteimportant">Only EL6 64bits and EL7 64bits package are available.
</div></p>
</p>
</div>
@ -123,13 +125,13 @@ Then install lasso and lasso-perl packages.
</p>
</div>
<!-- SECTION "Lasso" [717-1651] -->
<!-- SECTION "Lasso" [717-1484] -->
<h3><a name="apache_rewrite_rules" id="apache_rewrite_rules">Apache rewrite rules</a></h3>
<div class="level3">
<p>
Be sure that mod_rewrite is installed and that SAML2 rewrite rules are activated in <a href="../../documentation/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4:configlocation">Apache portal configuration</a>:
Be sure that mod_rewrite is installed and that SAML2 rewrite rules are activated in <a href="../../documentation/2.0/configlocation.html#portal" class="wikilink1" title="documentation:2.0:configlocation">Apache portal configuration</a>:
</p>
<pre class="code file apache">&lt;<span class="kw3">IfModule</span> mod_rewrite.c&gt;
<span class="kw1">RewriteEngine</span> <span class="kw2">On</span>
@ -138,7 +140,7 @@ Be sure that mod_rewrite is installed and that SAML2 rewrite rules are activated
&lt;/<span class="kw3">IfModule</span>&gt;</pre>
</div>
<!-- SECTION "Apache rewrite rules" [1652-1997] -->
<!-- SECTION "Apache rewrite rules" [1485-1830] -->
<h2><a name="service_configuration" id="service_configuration">Service configuration</a></h2>
<div class="level2">
@ -153,7 +155,7 @@ Go in Manager and click on <code><acronym title="Security Assertion Markup Langu
</p>
</div>
<!-- SECTION "Service configuration" [1998-2161] -->
<!-- SECTION "Service configuration" [1831-1994] -->
<h3><a name="entry_identifier" id="entry_identifier">Entry Identifier</a></h3>
<div class="level3">
@ -183,7 +185,7 @@ The value will be use in metadata main markup:
</p>
</div>
<!-- SECTION "Entry Identifier" [2162-2559] -->
<!-- SECTION "Entry Identifier" [1995-2392] -->
<h3><a name="security_parameters" id="security_parameters">Security parameters</a></h3>
<div class="level3">
@ -209,7 +211,7 @@ To define keys, you can:
</p>
<p>
<a href="/_detail/documentation/manager-saml-private-key.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:manager-saml-private-key.png"><img src="../../../media/documentation/manager-saml-private-key.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-saml-private-key.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:manager-saml-private-key.png"><img src="../../../media/documentation/manager-saml-private-key.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -218,13 +220,13 @@ To define keys, you can:
</p>
</div>
<!-- SECTION "Security parameters" [2560-3388] -->
<!-- SECTION "Security parameters" [2393-3221] -->
<h3><a name="nameid_formats" id="nameid_formats">NameID formats</a></h3>
<div class="level3">
<p>
<a href="/_detail/documentation/manager-saml-namid-formats.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:manager-saml-namid-formats.png"><img src="../../../media/documentation/manager-saml-namid-formats.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-saml-namid-formats.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:manager-saml-namid-formats.png"><img src="../../../media/documentation/manager-saml-namid-formats.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -232,7 +234,7 @@ To define keys, you can:
</p>
<p>
<p><div class="noteclassic">This parameter is used by <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML IDP</a> to fill the NameID in authentication responses.
<p><div class="noteclassic">This parameter is used by <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML IDP</a> to fill the NameID in authentication responses.
</div></p>
</p>
@ -252,7 +254,7 @@ Customizable NameID formats are:
<p>
<p><div class="notetip">For example, if you are using <a href="../../documentation/1.4/authldap.html" class="wikilink1" title="documentation:1.4:authldap">AD as authentication backend</a>, you can use sAMAccountName for the Windows NameID format.
<p><div class="notetip">For example, if you are using <a href="../../documentation/2.0/authldap.html" class="wikilink1" title="documentation:2.0:authldap">AD as authentication backend</a>, you can use sAMAccountName for the Windows NameID format.
</div></p>
</p>
@ -269,13 +271,13 @@ Other NameID formats are automatically managed:
</ul>
</div>
<!-- SECTION "NameID formats" [3389-4201] -->
<!-- SECTION "NameID formats" [3222-4034] -->
<h3><a name="authentication_contexts" id="authentication_contexts">Authentication contexts</a></h3>
<div class="level3">
<p>
<a href="/_detail/documentation/manager-saml-service-authn-contexts.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:manager-saml-service-authn-contexts.png"><img src="../../../media/documentation/manager-saml-service-authn-contexts.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-saml-service-authn-contexts.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:manager-saml-service-authn-contexts.png"><img src="../../../media/documentation/manager-saml-service-authn-contexts.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -283,7 +285,7 @@ Each <acronym title="LemonLDAP::NG">LL::NG</acronym> authentication module has a
</p>
<p>
<p><div class="noteclassic">This parameter is used by <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML IDP</a> to fill the authentication context in authentication responses. It will use the authentication level registered in user session to match the <acronym title="Security Assertion Markup Language">SAML</acronym> authentication context. It is also used by <a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML SP</a> to fill the authentication level in user session, based on authentication response authentication context.
<p><div class="noteclassic">This parameter is used by <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML IDP</a> to fill the authentication context in authentication responses. It will use the authentication level registered in user session to match the <acronym title="Security Assertion Markup Language">SAML</acronym> authentication context. It is also used by <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML SP</a> to fill the authentication level in user session, based on authentication response authentication context.
</div></p>
</p>
@ -302,7 +304,7 @@ Customizable NameID formats are:
</ul>
</div>
<!-- SECTION "Authentication contexts" [4202-4988] -->
<!-- SECTION "Authentication contexts" [4035-4821] -->
<h3><a name="organization" id="organization">Organization</a></h3>
<div class="level3">
@ -334,7 +336,7 @@ This concerns all parameters for the Organization metadata section:
</ul>
</div>
<!-- SECTION "Organization" [4989-5500] -->
<!-- SECTION "Organization" [4822-5333] -->
<h3><a name="service_provider" id="service_provider">Service Provider</a></h3>
<div class="level3">
@ -389,7 +391,7 @@ For each binding you can set:
<p>
<a href="/_detail/documentation/manager-saml-service-sp-slo.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:manager-saml-service-sp-slo.png"><img src="../../../media/documentation/manager-saml-service-sp-slo.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-saml-service-sp-slo.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:manager-saml-service-sp-slo.png"><img src="../../../media/documentation/manager-saml-service-sp-slo.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -422,7 +424,7 @@ For each binding you can set:
<p>
<a href="/_detail/documentation/manager-saml-service-sp-ac.png?id=documentation%3A1.4%3Asamlservice" class="media" title="documentation:manager-saml-service-sp-ac.png"><img src="../../../media/documentation/manager-saml-service-sp-ac.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager-saml-service-sp-ac.png?id=documentation%3A2.0%3Asamlservice" class="media" title="documentation:manager-saml-service-sp-ac.png"><img src="../../../media/documentation/manager-saml-service-sp-ac.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -446,7 +448,7 @@ The only authorized binding is <acronym title="Simple Object Access Protocol">SO
</p>
</div>
<!-- SECTION "Service Provider" [5501-6664] -->
<!-- SECTION "Service Provider" [5334-6497] -->
<h3><a name="identity_provider" id="identity_provider">Identity Provider</a></h3>
<div class="level3">
@ -552,7 +554,7 @@ The only authorized binding is <acronym title="Simple Object Access Protocol">SO
</p>
</div>
<!-- SECTION "Identity Provider" [6665-7653] -->
<!-- SECTION "Identity Provider" [6498-7486] -->
<h3><a name="attribute_authority" id="attribute_authority">Attribute Authority</a></h3>
<div class="level3">
@ -587,7 +589,7 @@ Response Location should be empty, as <acronym title="Simple Object Access Proto
</p>
</div>
<!-- SECTION "Attribute Authority" [7654-8065] -->
<!-- SECTION "Attribute Authority" [7487-7898] -->
<h3><a name="advanced" id="advanced">Advanced</a></h3>
<div class="level3">
@ -613,7 +615,7 @@ By default, the main session module is used to store <acronym title="Security As
</p>
<p>
This is not the case of <a href="../../documentation/1.4/memcachedsessionbackend.html" class="wikilink1" title="documentation:1.4:memcachedsessionbackend">Memcached</a> for example. In this case, you can choose a different module to manage <acronym title="Security Assertion Markup Language">SAML</acronym> sessions.
This is not the case of <a href="../../documentation/2.0/memcachedsessionbackend.html" class="wikilink1" title="documentation:2.0:memcachedsessionbackend">Memcached</a> for example. In this case, you can choose a different module to manage <acronym title="Security Assertion Markup Language">SAML</acronym> sessions.
</p>
<p>
@ -640,7 +642,7 @@ This is not the case of <a href="../../documentation/1.4/memcachedsessionbackend
</p>
<p>
The common domain is used by <a href="../../documentation/1.4/authsaml.html" class="wikilink1" title="documentation:1.4:authsaml">SAML SP</a> to find an Identity Provider for the user, and by <a href="../../documentation/1.4/idpsaml.html" class="wikilink1" title="documentation:1.4:idpsaml">SAML IDP</a> to register itself in user&#039;s IDP list.
The common domain is used by <a href="../../documentation/2.0/authsaml.html" class="wikilink1" title="documentation:2.0:authsaml">SAML SP</a> to find an Identity Provider for the user, and by <a href="../../documentation/2.0/idpsaml.html" class="wikilink1" title="documentation:2.0:idpsaml">SAML IDP</a> to register itself in user&#039;s IDP list.
</p>
<p>
@ -658,4 +660,26 @@ Configuration parameters are:
</ul>
</div>
<!-- SECTION "Advanced" [8066-] --></div><!-- closes <div class="dokuwiki export">-->
<!-- SECTION "Advanced" [7899-9925] -->
<h2><a name="replace_public_key_by_a_certificate" id="replace_public_key_by_a_certificate">Replace public key by a certificate</a></h2>
<div class="level2">
<p>
By default, <acronym title="LemonLDAP::NG">LL::NG</acronym> publish the public key in metadata, which may not fit to your partner SP or IDP. Here is a simple method to replace the public key by a certificate.
</p>
<ul>
<li class="level1"><div class="li"> Create the certificate from the private key as explained in <a href="../../documentation/2.0/applications/googleapps.html#certificate" class="wikilink1" title="documentation:2.0:applications:googleapps">Google Apps tutorial</a>.</div>
</li>
<li class="level1"><div class="li"> Now you have the certificate file, go in the Manager, go in the public key field and lod the certificate file.</div>
</li>
</ul>
<p>
That&#039;s all! If you look at the metadata, the certificate is now published!
</p>
</div>
<!-- SECTION "Replace public key by a certificate" [9926-] --></div><!-- closes <div class="dokuwiki export">-->

@ -51,7 +51,7 @@ This mechanism allow to do <acronym title="Single Sign On">SSO</acronym> on appl
<p>
Configure the virtual host like other <a href="../../documentation/1.4/configvhost.html" class="wikilink1" title="documentation:1.4:configvhost">protected virtual host</a> but use Secure Token Handler instead of default Handler.
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 Secure Token Handler instead of default Handler.
</p>
<pre class="code file apache">&lt;<span class="kw3">VirtualHost</span> *:80&gt;
<span class="kw1">ServerName</span> secure.example.com

@ -32,16 +32,16 @@
<p>
Configuration can be stored in several formats (<a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">SQL</a>, <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File</a>, <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP</a>) but must be shared over the network if you use more than 1 server. If some of your servers are not in the same (secured) network than the database, it is recommended to use <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP access</a> for those servers.
Configuration can be stored in several formats (<a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">SQL</a>, <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File</a>, <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP</a>) but must be shared over the network if you use more than 1 server. If some of your servers are not in the same (secured) network than the database, it is recommended to use <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP access</a> for those servers.
</p>
<p>
<p><div class="notetip">You can use different type of access: <a href="../../documentation/1.4/sqlconfbackend.html" class="wikilink1" title="documentation:1.4:sqlconfbackend">SQL</a>, <a href="../../documentation/1.4/fileconfbackend.html" class="wikilink1" title="documentation:1.4:fileconfbackend">File</a> or <a href="../../documentation/1.4/ldapconfbackend.html" class="wikilink1" title="documentation:1.4:ldapconfbackend">LDAP</a> for servers in secured network and <a href="../../documentation/1.4/soapconfbackend.html" class="wikilink1" title="documentation:1.4:soapconfbackend">SOAP</a> for remote servers.
<p><div class="notetip">You can use different type of access: <a href="../../documentation/2.0/sqlconfbackend.html" class="wikilink1" title="documentation:2.0:sqlconfbackend">SQL</a>, <a href="../../documentation/2.0/fileconfbackend.html" class="wikilink1" title="documentation:2.0:fileconfbackend">File</a> or <a href="../../documentation/2.0/ldapconfbackend.html" class="wikilink1" title="documentation:2.0:ldapconfbackend">LDAP</a> for servers in secured network and <a href="../../documentation/2.0/soapconfbackend.html" class="wikilink1" title="documentation:2.0:soapconfbackend">SOAP</a> for remote servers.
</div></p>
</p>
<p>
Next, you have to configure the <acronym title="Simple Object Access Protocol">SOAP</acronym> access as described <a href="../../documentation/1.4/soapconfbackend.html#next_configure_soap_for_your_remote_servers" class="wikilink1" title="documentation:1.4:soapconfbackend">here</a> since <acronym title="Simple Object Access Protocol">SOAP</acronym> access is denied by default.
Next, you have to configure the <acronym title="Simple Object Access Protocol">SOAP</acronym> access as described <a href="../../documentation/2.0/soapconfbackend.html#next_configure_soap_for_your_remote_servers" class="wikilink1" title="documentation:2.0:soapconfbackend">here</a> since <acronym title="Simple Object Access Protocol">SOAP</acronym> access is denied by default.
</p>
</div>
@ -102,7 +102,7 @@ To protect the manager by <acronym title="LemonLDAP::NG">LL::NG</acronym>, you j
<span class="re1">protection</span> <span class="sy0">=</span><span class="re2"> manager</span></pre>
<p>
<p><div class="noteimportant">Before, you have to create the virtual host <code>manager.your.domain</code> in the manager and set a <a href="../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">rules</a>, else access to the manager will be denied.
<p><div class="noteimportant">Before, you have to create the virtual host <code>manager.your.domain</code> in the manager and set a <a href="../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">rules</a>, else access to the manager will be denied.
</div></p>
</p>
@ -118,7 +118,7 @@ To protect the manager by <acronym title="LemonLDAP::NG">LL::NG</acronym>, you j
<p>
<a href="../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">Rules</a> are applied in alphabetical order (comment and regular expression). The first rule that matches is applied.
<a href="../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">Rules</a> are applied in alphabetical order (comment and regular expression). The first rule that matches is applied.
</p>
<p>
@ -131,7 +131,7 @@ The Manager let you define comments in rules, to order them:
</p>
<p>
<a href="/_detail/documentation/manager_access_rule.png?id=documentation%3A1.4%3Asecurity" class="media" title="documentation:manager_access_rule.png"><img src="../../../media/documentation/manager_access_rule.png" class="mediacenter" alt="" /></a>
<a href="/_detail/documentation/manager_access_rule.png?id=documentation%3A2.0%3Asecurity" class="media" title="documentation:manager_access_rule.png"><img src="../../../media/documentation/manager_access_rule.png" class="mediacenter" alt="" /></a>
</p>
<p>
@ -192,7 +192,7 @@ Use comment to correct this:
<p>
You can write <a href="../../documentation/1.4/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:1.4:writingrulesand_headers">rules</a> matching any component of <acronym title="Uniform Resource Locator">URL</acronym> to protect including GET parameters, but be careful.
You can write <a href="../../documentation/2.0/writingrulesand_headers.html#rules" class="wikilink1" title="documentation:2.0:writingrulesand_headers">rules</a> matching any component of <acronym title="Uniform Resource Locator">URL</acronym> to protect including GET parameters, but be careful.
</p>
<p>

@ -43,12 +43,12 @@ Your application can know the connected user using:
<p>
To get more information on user (name, mail, etc.), you have to read <a href="../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">HTTP headers</a>.
To get more information on user (name, mail, etc.), you have to read <a href="../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">HTTP headers</a>.
</p>
<p>
<p><div class="notetip">
If your application is based on <a href="http://search.cpan.org/perldoc?CGI" class="urlextern" title="http://search.cpan.org/perldoc?CGI" rel="nofollow">Perl CGI package</a>, you can simply replace <acronym title="Common Gateway Interface">CGI</acronym> by <a href="#perl_auto-protected_cgi" title="documentation:1.4:selfmadeapplication &crarr;" class="wikilink1">Lemonldap::NG::Handler::CGI</a>
If your application is based on <a href="http://search.cpan.org/perldoc?CGI" class="urlextern" title="http://search.cpan.org/perldoc?CGI" rel="nofollow">Perl CGI package</a>, you can simply replace <acronym title="Common Gateway Interface">CGI</acronym> by <a href="#perl_auto-protected_cgi" title="documentation:2.0:selfmadeapplication &crarr;" class="wikilink1">Lemonldap::NG::Handler::CGI</a>
</div></p>
</p>
@ -60,7 +60,7 @@ If your application is based on <a href="http://search.cpan.org/perldoc?CGI" cla
<p>
Examples with a <a href="../../documentation/1.4/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:1.4:writingrulesand_headers">configured header</a> named &#039;Auth-User&#039;:
Examples with a <a href="../../documentation/2.0/writingrulesand_headers.html#headers" class="wikilink1" title="documentation:2.0:writingrulesand_headers">configured header</a> named &#039;Auth-User&#039;:
</p>
</div>

Some files were not shown because too many files have changed in this diff Show More

Loading…
Cancel
Save