<divclass="noteimportant">LemonLDAP::NG does not manage Nginx configuration
@ -489,7 +491,7 @@ See <a href="confignginx.html" class="wikilink1" title="documentation:2.0:config
<divclass="notewarning"><ahref="fastcgiserver.html"class="wikilink1"title="documentation:2.0:fastcgiserver">LL::NG FastCGI</a> server must be loaded separately.
</div>
</div>
<!-- EDIT10 SECTION "Nginx" [11644-12097] -->
<!-- EDIT10 SECTION "Nginx" [11699-12152] -->
<h3class="sectionedit11"id="portal1">Portal</h3>
<divclass="level3">
@ -561,7 +563,7 @@ In Portal virtual host, you will find several configuration parts:
<divclass="noteclassic">As Handlers keep configuration in cache, when configuration change, it should be updated in Handlers. An Apache restart will work, but LemonLDAP::NG offers the mean to reload them through an HTTP request. Configuration reload will then be effective in less than 10 minutes.
@ -714,7 +717,7 @@ The <code>reload</code> target is managed in Apache or Nginx configuration, insi
<divclass="noteimportant">You must allow access to declared URLs to your Manager <abbrtitle="Internet Protocol">IP</abbr>.
@ -748,6 +751,6 @@ For example, to override configured skin for portal:
<divclass="notetip">You need to know the technical name of configuration parameter to do this. You can refer to <ahref="parameterlist.html"class="wikilink1"title="documentation:2.0:parameterlist">parameter list</a> to find it.
<h3class="sectionedit3"id="first_configure_your_real_backend">First, configure your real backend</h3>
<divclass="level3">
<ul>
<liclass="level1"><divclass="li"> On your main server, configure a <ahref="documentation/1.0/fileconfbackend.html"class="wikilink1"title="documentation:1.0:fileconfbackend">File</a>, <ahref="documentation/1.0/sqlconfbackend.html"class="wikilink1"title="documentation:1.0:sqlconfbackend">SQL</a> or <ahref="documentation/1.0/ldapconfbackend.html"class="wikilink1"title="documentation:1.0:ldapconfbackend">LDAP</a> backend</div>
</li>
<liclass="level1"><divclass="li"> Enable REST server in the configuration using the manager (in portal plugins)</div>
</li>
<liclass="level1"><divclass="li"> Configure Apache to allow remote access: in <code>portal-apache2.conf</code>, remote REST access is disabled by default. Change it:</div>
</li>
</ul>
<preclass="code apache"><spanclass="co1"># SOAP functions for configuration access (disabled by default)</span>
Now, <ahref="cda.html"class="wikilink1"title="documentation:2.0:cda">CDA</a>, <ahref="documentation/latest/applications/zimbra.html"class="wikilink1"title="documentation:latest:applications:zimbra">ZimbraPreAuth</a>, <ahref="securetoken.html"class="wikilink1"title="documentation:2.0:securetoken">SecureToken</a> and <ahref="handlerauthbasic.html"class="wikilink1"title="documentation:2.0:handlerauthbasic">AuthBasic</a> are <ahref="handlerarch.html"class="wikilink1"title="documentation:2.0:handlerarch">Handler Types</a>. So there is no more special file to load: you just have to choose “VirtualHost type” in the manager/VirtualHosts.
</p>
<ul>
<liclass="level1"><divclass="li"><ahref="cda.html"class="wikilink1"title="documentation:2.0:cda">CDA</a>, <ahref="documentation/latest/applications/zimbra.html"class="wikilink1"title="documentation:latest:applications:zimbra">ZimbraPreAuth</a>, <ahref="securetoken.html"class="wikilink1"title="documentation:2.0:securetoken">SecureToken</a> and <ahref="handlerauthbasic.html"class="wikilink1"title="documentation:2.0:handlerauthbasic">AuthBasic</a> are now <ahref="handlerarch.html"class="wikilink1"title="documentation:2.0:handlerarch">Handler Types</a>. So there is no more special file to load: you just have to choose “VirtualHost type” in the manager/VirtualHosts.</div>
</li>
<liclass="level1"><divclass="li"><strong>Apache only</strong>: because of an Apache behaviour change, PerlHeaderParserHandler must no more be used with “reload” URLs <em>(replaced by PerlResponseHandler)</em>. Any “reload url” that are inside a protected vhost must be unprotected in vhost rules <em>(protection has to be done by web server configuration)</em>.</div>
</li>
</ul>
</div>
<!-- EDIT7 SECTION "Handlers" [2071-2419] -->
<!-- EDIT7 SECTION "Handlers" [2071-2731] -->
<h2class="sectionedit8"id="rules_and_headers">Rules and headers</h2>
@ -192,12 +194,12 @@ Before 2.0, an Ajax query that was launched after session timeout received a 302
<divclass="noteimportant"><ahref="handlerauthbasic.html"class="wikilink1"title="documentation:2.0:handlerauthbasic">AuthBasic Handler</a> uses now REST services instead of SOAP.
Clément Oudot
8 years ago
