Configuration can be stored in several formats (<ahref="../../documentation/1.9/sqlconfbackend.html"class="wikilink1"title="documentation:1.9:sqlconfbackend">SQL</a>, <ahref="../../documentation/1.9/fileconfbackend.html"class="wikilink1"title="documentation:1.9:fileconfbackend">File</a>, <ahref="../../documentation/1.9/ldapconfbackend.html"class="wikilink1"title="documentation:1.9: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 <ahref="../../documentation/1.9/soapconfbackend.html"class="wikilink1"title="documentation:1.9:soapconfbackend">SOAP access</a> for those servers.
<p><divclass="notetip">You can use different type of access: <ahref="../../documentation/1.9/sqlconfbackend.html"class="wikilink1"title="documentation:1.9:sqlconfbackend">SQL</a>, <ahref="../../documentation/1.9/fileconfbackend.html"class="wikilink1"title="documentation:1.9:fileconfbackend">File</a> or <ahref="../../documentation/1.9/ldapconfbackend.html"class="wikilink1"title="documentation:1.9:ldapconfbackend">LDAP</a> for servers in secured network and <ahref="../../documentation/1.9/soapconfbackend.html"class="wikilink1"title="documentation:1.9:soapconfbackend">SOAP</a> for remote servers.
Next, you have to configure the SOAP access as described <ahref="../../documentation/1.9/soapconfbackend.html#next_configure_soap_for_your_remote_servers"class="wikilink1"title="documentation:1.9:soapconfbackend">here</a> since SOAP access is denied by default.
By default, the manager is restricted to the user 'dwho' (default backend is Demo). To protect the manager, you have to choose one or both of :
To protect the manager by <abbrtitle="LemonLDAP::NG">LL::NG</abbr>, you just have to set this in <code>lemonldap-ng.ini</code> configuration file (section [manager]):
<p><divclass="noteimportant">Before, you have to create the virtual host <code>manager.your.domain</code> in the manager and set a <ahref="../../documentation/1.9/writingrulesand_headers.html#rules"class="wikilink1"title="documentation:1.9:writingrulesand_headers">rules</a>, else access to the manager will be denied.
<ahref="../../documentation/1.9/writingrulesand_headers.html#rules"class="wikilink1"title="documentation:1.9:writingrulesand_headers">Rules</a> are applied in alphabetical order (comment and regular expression). The first rule that matches is applied.
You can write <ahref="../../documentation/1.9/writingrulesand_headers.html#rules"class="wikilink1"title="documentation:1.9:writingrulesand_headers">rules</a> matching any component of <abbrtitle="Uniform Resource Locator">URL</abbr> to protect including GET parameters, but be careful.
Some characters are encoded in URLs by the browser (such as space,…). To avoid problems, <abbrtitle="LemonLDAP::NG">LL::NG</abbr> decode them using <ahref="http://search.cpan.org/perldoc?Apache2::URI#unescape_url"class="urlextern"title="http://search.cpan.org/perldoc?Apache2::URI#unescape_url"rel="nofollow">http://search.cpan.org/perldoc?Apache2::URI#unescape_url</a>. So write your rules using normal characters.
See <ahref="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html"class="urlextern"title="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html"rel="nofollow">mod_proxy</a> and <ahref="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html"class="urlextern"title="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html"rel="nofollow">mod_rewrite</a> documentation for more about configuring Apache reverse-proxies.
</p>
<p>
Such configuration can have some security problems:
<liclass="level1"><divclass="li"> if a user can access directly to the hidden application, it can bypass <abbrtitle="LemonLDAP::NG">LL::NG</abbr> protection</div>
<liclass="level1"><divclass="li"> if many hidden applications are on the same private network, if one is corrupted (by SQL injection, or another attack), the hacker will be able to access to other applications without using reverse-proxies so it can bypass <abbrtitle="LemonLDAP::NG">LL::NG</abbr> protection</div>
It is recommended to secure the channel between reverse-proxies and application to be sure that only request coming from the <abbrtitle="LemonLDAP::NG">LL::NG</abbr> protected reverse-proxies are allowed. You can use one or a combination of:
<liclass="level1"><divclass="li"> SSL client certificate for the reverse-proxy (see SSLProxy* parameters in <ahref="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html"class="urlextern"title="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html"rel="nofollow">mod_ssl documentation</a>)</div>
Go in Manager, <code>General parameters</code> » <code>Advanced parameters</code> » <code>Security</code>:
</p>
<ul>
<liclass="level1"><divclass="li"><strong>Username control</strong>: Regular expression used to check user login syntax.</div>
</li>
<liclass="level1"><divclass="li"><strong>Force authentication</strong>: set to 'On' to force authentication when user connects to portal, even if he has a valid session</div>
<liclass="level1"><divclass="li"><strong>Force authentication interval</strong>: time interval (in seconds) when a authentication renewal cannot be forced, used to prevent to loose the current authentication during the main process. If you experience slow network performances, you can increase this value.</div>
<liclass="level1"><divclass="li"><strong>Encryption key</strong>: key used to crypt some data, should not be known by other applications</div>
</li>
<liclass="level1"><divclass="li"><strong>Trusted domains</strong>: domains on which the user can be redirected after login on portal. Set '*' to accept all.</div>
</li>
<liclass="level1"><divclass="li"><strong>Use Safe jail</strong>: set to 'Off' to disable Safe jail. Safe module is used to eval expressions in headers, rules, etc. Disabling it can lead to security issues.</div>
<liclass="level1"><divclass="li"><strong>Check <abbrtitle="Cross Site Scripting">XSS</abbr> Attacks</strong>: Set to 'Off' to disable <abbrtitle="Cross Site Scripting">XSS</abbr> checks. <abbrtitle="Cross Site Scripting">XSS</abbr> checks will still be done with warning in logs, but this will not prevent the process to continue.</div>
You can change the module used for sessions identifier generation. To do, add <code>generateModule</code> key in the configured session backend options.
</p>
<p>
We recommend the use of <code>Lemonldap::NG::Common::Apache::Session::Generate::SHA256</code>.
