<liclass="level1"><divclass="li"><strong>adminSessions/</strong>: read/write access to sessions (required for distant Portal, distant Manager or distant Handlers which modify sessions)</div>
This session backend can be used to share sessions stored in a non-network backend (like <ahref="../../documentation/2.0/filesessionbackend.html"class="wikilink1"title="documentation:2.0:filesessionbackend">file session backend</a>) or in a network backend protected with a firewall that only accepts HTTP flows.
To configure it, SOAP session backend will be set trough Manager in global configuration (used by all Hanlders), and the real session backend will be configured for local components in lemonldap-ng.ini.
Then, set <code>Lemonldap::NG::Common::Apache::Session::SOAP</code> in <code>General parameters</code> » <code>Sessions</code> » <code>Session storage</code> » <code>Apache::Session module</code> and add the following parameters (case sensitive):
<tdclass="col0 centeralign"><strong>proxy</strong></td><tdclass="col1"><abbrtitle="Uniform Resource Locator">URL</abbr> of sessions SOAP end point </td><tdclass="col2"> http://auth.example.com/index.pl/sessions </td>
Sessions SOAP end points access must be allowed in Apache portal configuration (for example, access by <abbrtitle="Internet Protocol">IP</abbr> range):
Real session backend will be configured in <code>lemonldap-ng.ini</code>, in <code>portal</code> section (the portal hosts the SOAP service for sessions, and will do the link between SOAP requests and real sessions).
For example, if real sessions are stored in <ahref="../../documentation/2.0/filesessionbackend.html"class="wikilink1"title="documentation:2.0:filesessionbackend">files</a>:
<p><divclass="notetip">If your sessions explorer is on the same server that the portal, either use the <strong>adminSessions</strong> end point in Manager configuration, or override the <code>globalStorage</code> and <code>globalStorageOptions</code> parameters in section all (and not portal) of <code>lemonldap-ng.ini</code>.