SOAP Session backend

This documentation is available only for version 0.9.4 and later. For earlier versions, see the documentation in the source tree.

Presentation

As the SOAP Configuration backend, the SOAP Session backend allow distant access to session database.

To work, the main Portal will have a direct access to the real session database (for example files, MySQL or LDAP). Remote components will send SOAP request to main portal to read and write sessions.

Configuration

Main Portal

To activate SOAP in main Portal, just set: 
Soap => 1,


You have also to override the configuration of session database, with a file backend for example: 
globalStorage => 'Apache::Session::File',
  globalStorageOptions => {
    Directory     => '/var/lib/lemonldap-ng/sessions/',
    LockDirectory => '/var/lib/lemonldap-ng/sessions/lock/',
}

You have also to update Apache configuration to allow SOAP requests. Add this in the main Portal virtual host: 
<Location /index.pl/sessions>
    Order deny,allow
    Deny from all
    Allow from *remote servers*
</Location>

Remote components

Remote components will use the main configuration. So use the Manager to configure the session database with this value: 
Lemonldap::NG::Common::Apache::Session::SOAP


Set also this Session Storage option: 
proxy => 'http://auth.example.com/index.pl/sessions'


No other parameters needed. It will send SOAP request to configured proxy URL.