128 lines
6.0 KiB
HTML
128 lines
6.0 KiB
HTML
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
|
|
lang="en" dir="ltr">
|
|
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title></title>
|
|
<!-- metadata -->
|
|
<meta name="generator" content="Offline" />
|
|
<meta name="version" content="Offline 0.1" />
|
|
<!-- style sheet links -->
|
|
<link rel="stylesheet" media="all" type="text/css" href="../../../css/all.css" />
|
|
<link rel="stylesheet" media="screen" type="text/css" href="../../../css/screen.css" />
|
|
<link rel="stylesheet" media="print" type="text/css" href="../../../css/print.css" />
|
|
|
|
</head>
|
|
<body>
|
|
<div class="dokuwiki export">
|
|
|
|
|
|
<h1 class="sectionedit1" id="soap_session_backend">SOAP session backend</h1>
|
|
<div class="level1">
|
|
|
|
<p>
|
|
<abbr title="LemonLDAP::NG">LL::NG</abbr> portal provides SOAP end points for sessions management:
|
|
</p>
|
|
<ul>
|
|
<li class="level1"><div class="li"> <strong>sessions/</strong>: read only access to sessions (enough for distant Handlers)</div>
|
|
</li>
|
|
<li class="level1"><div class="li"> <strong>adminSessions/</strong>: read/write access to sessions (required for distant Portal, distant Manager or distant Handlers which modify sessions)</div>
|
|
</li>
|
|
</ul>
|
|
|
|
<p>
|
|
This session backend can be used to share sessions stored in a non-network backend (like <a href="../../documentation/1.9/filesessionbackend.html" class="wikilink1" title="documentation:1.9:filesessionbackend">file session backend</a>) or in a network backend protected with a firewall that only accepts HTTP flows.
|
|
</p>
|
|
|
|
<p>
|
|
Most of the time, SOAP session backend is used by Handlers installed on external servers.
|
|
</p>
|
|
|
|
<p>
|
|
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.
|
|
</p>
|
|
|
|
</div>
|
|
<!-- EDIT1 SECTION "SOAP session backend" [1-832] -->
|
|
<h2 class="sectionedit2" id="setup">Setup</h2>
|
|
<div class="level2">
|
|
|
|
</div>
|
|
<!-- EDIT2 SECTION "Setup" [833-851] -->
|
|
<h3 class="sectionedit3" id="manager">Manager</h3>
|
|
<div class="level3">
|
|
|
|
<p>
|
|
First, active SOAP in <code>General parameters</code> » <code>Advanced parameters</code> » <code>SOAP</code>.
|
|
</p>
|
|
|
|
<p>
|
|
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):
|
|
</p>
|
|
<div class="table sectionedit4"><table class="inline">
|
|
<thead>
|
|
<tr class="row0 roweven">
|
|
<th class="col0 centeralign" colspan="3"> Required parameters </th>
|
|
</tr>
|
|
<tr class="row1 rowodd">
|
|
<th class="col0 centeralign"> Name </th><th class="col1 centeralign"> Comment </th><th class="col2 centeralign"> Example </th>
|
|
</tr>
|
|
</thead>
|
|
<tr class="row2 roweven">
|
|
<td class="col0 centeralign"> <strong>proxy</strong> </td><td class="col1"> <abbr title="Uniform Resource Locator">URL</abbr> of sessions SOAP end point </td><td class="col2"> http://auth.example.com/index.pl/sessions </td>
|
|
</tr>
|
|
</table></div>
|
|
<!-- EDIT4 TABLE [1163-1322] -->
|
|
<p>
|
|
<p><div class="notetip">Use /adminSessions if the Handler need to modify the session, for example if you configured an idle timeout.
|
|
</div></p>
|
|
</p>
|
|
|
|
</div>
|
|
<!-- EDIT3 SECTION "Manager" [852-1450] -->
|
|
<h3 class="sectionedit5" id="apache">Apache</h3>
|
|
<div class="level3">
|
|
|
|
<p>
|
|
Sessions SOAP end points access must be allowed in Apache portal configuration (for example, access by <abbr title="Internet Protocol">IP</abbr> range):
|
|
</p>
|
|
<pre class="code file apache"><span class="co1"># SOAP functions for sessions management (disabled by default)</span>
|
|
<<span class="kw3">Location</span> /index.pl/adminSessions>
|
|
<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 192.168.2.0/<span class="nu0">24</span>
|
|
</<span class="kw3">Location</span>>
|
|
|
|
<span class="co1"># SOAP functions for sessions access (disabled by default)</span>
|
|
<<span class="kw3">Location</span> /index.pl/sessions>
|
|
<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 192.168.2.0/<span class="nu0">24</span>
|
|
</<span class="kw3">Location</span>></pre>
|
|
|
|
</div>
|
|
<!-- EDIT5 SECTION "Apache" [1451-1956] -->
|
|
<h3 class="sectionedit6" id="real_session_backend">Real session backend</h3>
|
|
<div class="level3">
|
|
|
|
<p>
|
|
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).
|
|
</p>
|
|
|
|
<p>
|
|
For example, if real sessions are stored in <a href="../../documentation/1.9/filesessionbackend.html" class="wikilink1" title="documentation:1.9:filesessionbackend">files</a>:
|
|
</p>
|
|
<pre class="code file ini"><span class="re0"><span class="br0">[</span>portal<span class="br0">]</span></span>
|
|
<span class="re1">globalStorage</span> <span class="sy0">=</span><span class="re2"> Apache::Session::File</span>
|
|
<span class="re1">globalStorageOptions</span> <span class="sy0">=</span><span class="re2"> <span class="br0">{</span> 'Directory' <span class="sy0">=</span>> '/var/lib/lemonldap-ng/sessions/', 'LockDirectory' <span class="sy0">=</span>> '/var/lib/lemonldap-ng/sessions/lock/', <span class="br0">}</span></span></pre>
|
|
|
|
<p>
|
|
<p><div class="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>.
|
|
</div></p>
|
|
</p>
|
|
|
|
</div>
|
|
</div><!-- closes <div class="dokuwiki export">--> |