Apache::AuthCookieDBIRadius An AuthCookie module backed by a DBI database, and an optional Radius server.
Download

Apache::AuthCookieDBIRadius Ranking & Summary

Apache::AuthCookieDBIRadius Tags

server Perl module Radius radius server AuthCookie module AuthCookie

Apache::AuthCookieDBIRadius Description

An AuthCookie module backed by a DBI database, and an optional Radius server. Apache::AuthCookieDBIRadius is an AuthCookie module backed by a DBI database, and an optional Radius server.SYNOPSIS # In httpd.conf or .htaccess ############################################ # AuthCookie # # # # PortalDBI_CryptType # # PortalDBI_GroupsTable # # PortalDBI_GroupField # # PortalDBI_GroupUserField # # PortalDBI_EncryptionType none|crypt|md5 # # PortalDBI_a on|off # # PortalDBI_b on|off # # PortalDBI_c on|off # # PortalDBI_d on|off # # PortalDBI_e on|off # # PortalDBI_f on|off # # PortalDBI_g on|off # # PortalDBI_useracct on|off # # PortalDBI_log_field last_access # # PortalDBI_Radius_host none # # PortalDBI_Radius_port 1645 # # PortalDBI_Radius_secret none # # PortalDBI_Radius_timeout 45 # # AuthCookieDebug 0,1,2,3 # # PortalDomain .yourdomain.com # # # ############################################ # key line must come first PerlSetVar PortalDBI_SecretKeyFile /usr/local/apache/conf/site.key PerlModule Apache::AuthCookieDBIRadius PerlSetVar PortalPath / PerlSetVar PortalLoginScript /login.pl PerlSetVar AuthCookieDebug 1 PerlSetVar PortalDBI_DSN 'dbi:Pg:host=localhost port=5432 dbname=mydatabase' PerlSetVar PortalDBI_User "database_user" PerlSetVar PortalDBI_Password "database_password" PerlSetVar PortalDBI_UsersTable "users" PerlSetVar PortalDBI_UserField "userid" PerlSetVar PortalDBI_PasswordField "password" PerlSetVar PortalDBI_SessionLifeTime 00-24-00-00 < FilesMatch ".pl" > AuthType Apache::AuthCookieDBIRadius AuthName Portal SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI < /FilesMatch > # login.pl < Files LOGIN > AuthType Apache::AuthCookieDBIRadius AuthName Portal SetHandler perl-script PerlHandler Apache::AuthCookieDBIRadius->login < /Files > ####################################### # # # Begin websites # # # ####################################### # private < Directory /home/httpd/html/private > AuthType Apache::AuthCookieDBIRadius AuthName Portal PerlSetVar PortalDBI_b on PerlAuthenHandler Apache::AuthCookieDBIRadius->authenticate PerlAuthzHandler Apache::AuthCookieDBIRadius->authorize require valid-user < /Directory > # calendar < Directory /home/httpd/html/calendar > AuthType Apache::AuthCookieDBIRadius AuthName Portal PerlSetVar PortalDBI_a on PerlAuthenHandler Apache::AuthCookieDBIRadius->authenticate PerlAuthzHandler Apache::AuthCookieDBIRadius->authorize require valid-user < /Directory >This module is an authentication handler that uses the basic mechanism provided by Apache::AuthCookie with a DBI database for ticket-based protection. It is based on two tokens being provided, a username and password, which can be any strings (there are no illegal characters for either). The username is used to set the remote user as if Basic Authentication was used.On an attempt to access a protected location without a valid cookie being provided, the module prints an HTML login form (produced by a CGI or any other handler; this can be a static file if you want to always send people to the same entry page when they log in). This login form has fields for username and password. On submitting it, the username and password are looked up in the DBI database. The supplied password is checked against the password in the database; the password in the database can be plaintext, or a crypt() or md5_hex() checksum of the password. If this succeeds, the user is issued a ticket. This ticket contains the username, an issue time, an expire time, and an MD5 checksum of those and a secret key for the server. It can optionally be encrypted before returning it to the client in the cookie; encryption is only useful for preventing the client from seeing the expire time. If you wish to protect passwords in transport, use an SSL-encrypted connection. The ticket is given in a cookie that the browser stores.After a login the user is redirected to the location they originally wished to view (or to a fixed page if the login "script" was really a static file).On this access and any subsequent attempt to access a protected document, the browser returns the ticket to the server. The server unencrypts it if encrypted tickets are enabled, then extracts the username, issue time, expire time and checksum. A new checksum is calculated of the username, issue time, expire time and the secret key again; if it agrees with the checksum that the client supplied, we know that the data has not been tampered with. We next check that the expire time has not passed. If not, the ticket is still good, so we set the username.Authorization checks then check that any "require valid-user" or "require user jacob" settings are passed. Finally, if a "require group foo" directive was given, the module will look up the username in a groups database and check that the user is a member of one of the groups listed. If all these checks pass, the document requested is displayed.If a ticket has expired or is otherwise invalid it is cleared in the browser and the login form is shown again. Requirements: · Perl

Apache::AuthCookieDBIRadius Related Software