Free wikid strong authentication system 3.0.10 software for linux

OpenVPN authentication server is a project which allows you to add very flexible authentication for your OpenVPN server.
OpenVPN authentication server provides very flexible authentication (LDAP, Kerberos, Radius, PAM, SASL, File, SQL, IMAP, POP3) for your OpenVPN server. You can also retrieve per-client configuration in your LDAP server.
Main features:
- Very flexible authentication configuration
- Chainable authentication backends. You can mix several authentication backends
- Authentication server written in perl
- Authentication server can run completely in chroot (recommended)
- Authentication client written in C
- Authentication client can run completely in chroot if OpenVPN server is chrooted
- Supports almost all existing authentication backends.
- Supported authentication backends:
- LDAP
- Kerberos5 (works also with Microsoft AD)
- any SQL database supported by perl DBI driver
- IMAPv4 server
- POP3 server
- plain file
- SASL library
- PAM library
- Radius service
- custom certificate validation algorithm.

NTLM authentication library (libntlm) is a library that implement Microsofts NTLM authentication.
However, the packaging of libntlm lacked certain things, such as having build problems, lacking shared library support, lacking autoconf macro for use in other applications, lacking pkg-config support, and more. So this page distributes an improved version of the library; called Libntlm.
Libntlm is licensed under the GNU Lesser General Public License.
Projects using Libntlm include GNU SASL.
Enhancements:
- This release adds new APIs to access the SMBencrypt and SMBNTencrypt functions.
- The library is now linked with -no-undefined to enable building a Windows DLL.

Directory Server NT Authentication Module provides a plugin allowing LDAP authentication via an NT domain account.
The Directory Server NT Authentication Module project is made of two parts: The first is a simple daemon which takes an NT users domain credentials (including password) and attempts to authenticate via the SMB protocol with those credentials.
The second part is a plugin which takes an LDAP DN and password and discovers the DNs NT domain identifier (if the entry has such an ID).
The daemon will only listen on localhost, so the credentials are not exposed via the network, and it does not run as root, so that compromise can be limited.
It attempts to locate all the domain controllers for an arbitrary domain, so failure of one DC does not cause the module to fail the authentication attempt unless no DC can be found that will accept the credential.
Enhancements:
- Minor change - new parameter in ntauth-config.txt "null_password_fail". If set to non-zero, then this causes a password bind with a non-NULL dn and a NULL password to generate "INVALID CREDENTIALS". By default, this parameter is off (which means silently assign the anonymous identity to the post bind LDAP session - which is the correct thing to do, according to the LDAP spec).

Courier Authentication Library is an API toolkit for implementing password validation and account metadata lookups. Copies of this library code used to exist in other tarballs: Courier, Courier-IMAP, and SqWebMail. Building and installing any of these packages wouldve automatically installed this authentication code.
The authentication library is now a separate, standalone package. This authentication library must now be installed, separately, before upgrading to the following builds (or if installing them for the first time): Courier 0.48, Courier-IMAP 4.0, and SqWebMail 5.0.
The Courier authentication library provides authentication services for other Courier applications. In this context, the term "authentication" refers to the following functions:
1. Take a userid or a loginid, and a password. Determine whether the loginid and the password are valid.
2. Given a userid, obtain the following information about the userid:
A. The accounts home directory.
B. The numeric system userid and groupid that owns all files associated with this account.
C. The location of the accounts maildir.
D. Any maildir quota defined for this account. See the Courier documentation for more information on maildir quotas.
E. Other miscellaneous account-specific options.
3. Change the password associated with a loginid.
4. Obain a complete list of all loginids.
The Courier authentication library provides alternative implementations of these authentication services:
1. Use the traditional system password files: /etc/passwd and /etc/shadow, possibly in conjunction with the PAM library.
2. Maintain all this information in a GDBM or a DB database. The GDBM or the DB database is compiled from plain text files. Perl scripts provide a simple interface for creating and editing the authentication information, then a script compiles the plain text files into a database.
3. Use an LDAP server for authentication.
4. Use a table in a MySQL database for authentication.
5. Use a table in a PostgreSQL database for authentication.
All Courier components that use this authentication library, therefore, will be able to authenticate E-mail accounts using any of the above methods.
Enhancements:
- This release fixes many compiler warnings, updates the LDAP API to OpenLDAP 2.3, tweaks the Makefile to make Solariss linker happy, and cleans up the RPM spec file.

CGI::Application::Plugin::Authentication::Driver is a Perl base module for building driver clasees for CGI::Application::Plugin::Authentication.

SYNOPSIS

package CGI::Application::Plugin::Authentication::Driver::MyDriver;
use base qw(CGI::Application::Plugin::Authentication::Driver);

sub verify_credentials {
my $self = shift;
my @credentials = @_;

if ( >>> Validate Credentials [ DBI,
DSN => ...,
TABLE => users,
CONSTRAINTS => {
username => __CREDENTIAL_1__,
MD5:password => __CREDENTIAL_2__,
}
],

Here we are saying that the password field is encoded using an MD5 hash, and should be checked accordingly.

PHP-Authentication provides a Tomcat-like authentication for PHP.
You give the source to authenticate against (DB, file, XML-RPC, etc.) and the directories that shall be protected, and the class handles the rest.
No including of any call to a class method on every page is necessary. You can also use it as if it were a standard Auth-class, using a call to "isLoggedIn" on every page that shall be protected.
Whats New in 1.3.3 Release:
- added logging, use option logFile
- clean up the session handling, remove global-use
- fix some win-issues
- optimize the isUrlProtected method, to work better on win
Whats New in 1.3.5 Release:
- first implementation of SOAP

CGI::Application::Plugin::Authentication::Driver::DBI is a DBI Authentication driver.

SYNOPSIS

use base qw(CGI::Application);
use CGI::Application::Plugin::Authentication;

__PACKAGE__->authen->config(
DRIVER => [ DBI,
DBH => $self->dbh,
TABLE => user,
CONSTRAINTS => {
user.name => __CREDENTIAL_1__,
MD5:user.password => __CREDENTIAL_2__
},
],
);

This Authentication driver uses the DBI module to allow you to authenticate against any database for which there is a DBD module. You can either provide an active database handle, or provide the parameters necesary to connect to the database.
When describing the database structure, you need to specify some or all of the following parameters: TABLE(S), JOIN_ON, COLUMNS and CONSTRAINTS.

DBH

The DBI database handle to use. Defaults to $self-dbh()>, which is provided and configured through CGI::Application::Plugin::DBH

TABLE(S) (required)

Provide either a single table name, or an array of table names. You can give the table names aliases which can be referenced in later columns.

TABLE => users,

- or -

TABLES => [users U, domains D],
JOIN_ON (conditionally required)
If you have specified multiple tables, then you need to provide an SQL expression that can be used to join those tables.
JOIN_ON => user.domainid = domain.id,

- or -

JOIN_ON => U.domainid = D.id,