mod_auth_remedy 2.0.0 review

mod_auth_remedy is an Apache module for HTTP Basic authentication/authorization in the Remedy Action Request System (ARS). Users o

License: The Apache License 2.0 File size: 0K Developer: Rafal Michalski

0

mod_auth_remedy is an Apache module for HTTP Basic authentication/authorization in the Remedy Action Request System (ARS).

Users of the Remedy Action Request System are organized in groups as in UNIX. Each user may belong to several groups. Users log into server using passwords. ARS stores information in so-called schemas, an analogue of tables in a relational database. Schemas have records.

There is a schema named User storing user information such as Login Name and Password, one record for each user. This schema corresponds to /etc/passwd on UNIX. Another schema named Group stores information about groups - it is for ARS what /etc/group is for UNIX.

On HTTP request to a constrained URL, the browser supplies Apache with username and password typed in the Basic authentication box. The module opens connection to the Remedy server RemedyServer as user RemedyBindName with password RemedyBindPass, and seeks the User schema for record with Login Name equal to the browser-supplied username.

Only if the record exists and contains password that matches the browser-supplied password, the module tells Apache to let the user in. If RemedyBindName directive is < None >, the module attempts to log onto Remedy staighfoward with browser-supplied username/password and if this login succeeds, it lets to access the URL.

The User schema record contains list of groups the user belongs to. This list is compared to the content of the standard Require group directive in the authorization phase.

Directives

The module supports the following run-time configuration directives:

RemedyAuthoritative (On|Off)
whether other modules will attempt authentication (Off) or not (On)
RemedyServer
Remedy Action Request System server machine name
RemedyBindName
Remedy user login under which Apache can connect to the Remedy server. This Remedy user should have read permissions on the Password field in the User schema. When set to , Apache will use the login supplied by browser, i. e. login typed in in the auth box.
RemedyBindPass
password of the Remedy user. Set to when the previous is set to
RemedyAPILog (On|Off)
enables intensive logging of module operations.