NAME
Lemonldap::NG::Portal::Main::Plugin - Base class for Lemonldap::NG::Portal modules (plugins, authentication modules,...).
SYNOPSIS
package Lemonldap::NG::Portal::My::Plugin;
use Mouse;
extends 'Lemonldap::NG::Portal::Main::Plugin';
use constant beforeAuth => 'verifyIP';
sub init {
my ($self) = @_;
$self->addUnauthRoute( mypath => 'hello', [ 'GET', 'PUT' ] );
$self->addAuthRoute( mypath => 'wellcome', [ 'GET', 'PUT' ] );
return 1;
}
sub verifyIP {
my ($self, $req) = @_;
return PE_ERROR if($req->address !~ /^10/);
return PE_OK;
}
sub hello {
my ($self, $req) = @_;
...
return $self->p->sendJSONresponse($req, { hello => 1 });
}
sub wellcome {
my ($self, $req) = @_;
...
return $self->p->sendHtml($req, 'template', params => { WELLCOME => 1 });
}
DESCRIPTION
Lemonldap::NG::Portal::Main::Plugin provides many methods to write easily Lemonldap::NG addons.
init() is called for each plugin. If one plugin initialization fails (init() returns 0), the portal responds a 500 status code for each request.
Writing plugins
Custom plugins can be inserted in portal by declaring them in lemonldap-ng.ini
file, section [portal]
, key customPlugins
:
[portal]
customPlugins = My::Plugin1, My::Plugin2
Plugins must be valid packages well found in @INC
.
Plugin entry points
Entry point based on PATH_INFO
Plugins can declare unauthRoutes/authRoutes during this initialization (= /path/info). Methods declared in this way must be declared in the plugin class. They will be called this the $req argument: the HTTP request (Lemonldap::NG::Portal::Main::Request). These methods must return a valid PSGI response. You can also use sendJSONresponse() or sendHtml() methods (see Lemonldap::NG::Common::PSGI).
Example:
sub init {
my ($self) = @_;
$self->addUnauthRoute( mypath => 'hello', [ 'GET', 'PUT' ] );
$self->addAuthRoute( mypath => 'wellcome', [ 'GET', 'PUT' ] );
return 1;
}
sub hello {
my ($self, $req) = @_;
...
return $self->p->sendJSONresponse($req, { hello => 1 });
}
sub wellcome {
my ($self, $req) = @_;
...
return $self->p->sendHtml($req, 'template', params => { WELLCOME => 1 });
}
Entry point in auth process
A plugin which wants to be inserted in authentication process has to declare constants containing the name of the method to run. The following entry points are available.
beforeAuth
: method called before authentication processbetweenAuthAndDatas
: method called after authentication and before settingsessionInfo
provisionningafterDatas
: method called aftersessionInfo
provisionning (macros, groups,...)forAuthUser
: method called for already authenticated usersbeforeLogout
: method called before logout
Note: methods inserted so must return a PE_* constant. See Lemonldap::NG::Portal::Main::Constants.
SEE ALSO
OTHER POD FILES
- Writing an authentication module: Lemonldap::NG::Portal::Auth::Base
- Writing an issuer module: Lemonldap::NG::Portal::Main::Issuer
- Request object: Lemonldap::NG::Portal::Main::Request
- Adding parameters in the manager: Lemonldap::NG::Manager::Build
AUTHORS
- LemonLDAP::NG team http://lemonldap-ng.org/team
BUG REPORT
Use OW2 system to report bug or ask for features: http://jira.ow2.org
DOWNLOAD
Lemonldap::NG is available at http://forge.objectweb.org/project/showfiles.php?group_id=274
COPYRIGHT AND LICENSE
See COPYING file for details.
This library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.