Free auth software for linux

Auth MemCookie is an Apache v2 authentification and authorization modules are based on "cookie" authentification mecanism.

The module dont make authentification by it self, but verify if authentification "the cookie" are valid for each url protected by the module. The module validate also if the "authentificated user" have authorisation to acces url.

Authentification are made externaly by an authentification form page and all authentification information nessary to the module a stored in memcached indentified by the cookie value "authentification session id" by this login page.

How it Works

Phase 1 : The login Form

Authentification are made by a login formular page.
This login page must authenticate the user with any authenticate source (ldap, /etc/password, file, database....) accessible to langage of the page (php, perl, java... an ldap login page sample in php are in samples directory).

Then must set cookie that contain only a key the "authentification unique id" of the "authentification session".

The login page must store authorisation and user information of the authenticated user in memcached identified by the cookie key "authentification unique id".

The login page can be developted in any langage you want, but must be capable to use memcached (they must have memcache client api for us)

Phase 2 : The Apache v2 Module

After the user are logged, the apache 2 module check on each protected page by apache ACL the presence of the "cookie".

if the "cookie" exist, try to get session in memcached with the "cookie" value if not found return "HTTP_UNAUTHORIZED" page.

if session exist in memcached verify if acl match user session information if not match return "HTTP_FORBIDDEN" page.

OpenVPN Auth Passwd is a plugin that authenticates OpenVPN users using the local passwd or shadow files, using a privilege separation model.
OpenVPN Auth Passwds authentication method must be defined in the Makefile prior to the compilation of the plugin.
On shadowed systems it uses the functions provided in the shadow suite and, on other systems, the getpwnam(3) function to verify the username/password.
SYNOPSIS
The openvpn-auth-passwd module implements username/password authentication via the passwd files and, in the systems with shadow support, we use it. It is provided for systems that dont have PAM.
This module uses a split privilege execution model, the same used in the auth-pam and down-root plugins. That is, even if you drop the openvpn daemon privileges using the user, group, or chroot directives, the plugin still work.
BUILD
To build openvpn-auth-passwd on systems that use shadow, you will need to have the shadow suite and its devel headers installed.
On GNU systems build with the "make" command. In other systems you should install the GNU make, if you dont have it, and type "gmake". The module will be named openvpn-auth-passwd.so
USAGE
To use this plugin module, add to your OpenVPN config file:
plugin openvpn-auth-passwd.so
Run OpenVPN with --verb 7 or higher to get debugging output from this plugin.
CAVEATS
This module is supposed to work on any *nix system but, more testing should be done. Right now it works in the Linux and OpenBSD.
There is no portable way to check if you are using the shadow suite or not. And, as we are not using autoconf to do this, you must manually set the USE_SHADOW directive in the Makefile. We assume by default that you are using it (the majority of linux distributions and sun). If you arent (the majority of *bsd systems and others),
you should set it to 0.
Enhancements:
- Added a new funtion to check if the user belong to a given group or not.

CGI::Builder::Auth::UserAdmin is a Perl module for the management of HTTP server user databases.

SYNOPSIS

use CGI::Builder::Auth::UserAdmin ();

Pay no attention to that man behind the curtain! Move along, nothing to see here!

This module was originally part of the HTTPD-User-Manage collection, which is available on CPAN. If you want to use it, go download that package. This module is used as part of the internal implementation of CGI::Builder::Auth. The original documentation is preserved here in this release for historical purposes. The software has been hacked and this documentation is not guaranteed to be correct. The module may disappear from the CGI::Builder::Auth distribution in a future release. Do not use it directly or rely on it.
This software is meant to provide a generic interface that hides the inconsistencies across HTTP server implementations of user and group databases.

METHODS

new ()

Heres where we find out whats different about your server.

Some examples:

@DBM = (DBType => DBM,
DB => .htpasswd,
Server => apache);

$user = new CGI::Builder::Auth::UserAdmin @DBM;

This creates an object whos database is a DBM file named .htpasswd, in a format that the Apache server understands.

@Text = (DBType => Text,
DB => .htpasswd,
Server => ncsa);

$user = new CGI::Builder::Auth::UserAdmin @Text;

This creates an object whose database is a plain text file named .htpasswd, in a format that the NCSA server understands.

@SQL = (DBType => "SQL",
Host => "", #server hostname
Port => "", #server port
DB => "www", #database name
User => "", #database login name
Auth => "", #database login password
Encrypt => "crypt", #encryption method
Driver => "mSQL", #driver for DBI
Server => "apache", #HTTP server type, not required
UserTable => "www-users", #table with field names below
NameField => "user", #field for the name
PasswordField => "password", #field for the password
);

$user = new CGI::Builder::Auth::UserAdmin @SQL;

This creates an object whos mSQL database is named www, with a schema that the Apache server (extention) understands.

ftp4che is an FTP library for Java 1.4 and 5.0 that features support for implicit SSL, implicit AUTH SSL, AUTH TLS, TLS, FXP, PRET, SSCN, an event model, bandwidth control, and unlimited file sizes.

squid-imap provides a piece of oftware to authenticate squid users via an IMAP server.

squid-imap is a basic squid auth helper that authenticates usernames and passwords via an IMAP server.

SYNOPSIS

# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);

# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );

die "oops: ".$c->lastError unless $c->connect();

$c->register_beat(10, &every_10_seconds);

$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);

$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth

$c->send( );

$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.

Rodent is an ident daemon that is capable of routing AUTH requests to other machines on your network.

Rodent is intended for routers or to be run on a machine behind a home router.

Rodent allows others to enjoy full ident without the limitations of port forwarding to a single machine.