RADIUS module ============= The RADIUS module provides a single authentication module: `radius:Radius` : Authenticate a user against a RADIUS server. This authentication module contacts a RADIUS server, and authenticates the user by using username & password authentication. To use this module, enable the radius module by creating a file named `enable` in the `modules/radius/`-directory. Then you need to add a authentication source which uses the `radius:Radius` module to `config/authsources.php`: 'example-radius' => array( 'radius:Radius', /* * An array with the radius servers to use, up to 10. * The options are: * - hostname: the hostname of the radius server, or its IP address. Required. * - port: the port of the radius server. Optional, defaults to 1812. * - secret: the radius secret to use with this server. Required. */ 'servers' => array(array('hostname' => 'radius1.example.org', 'port' => 1812, 'secret' => 'topsecret'), array('hostname' => 'radius2.example.org', 'port' => 1812, 'secret' => 'topsecret')), /* * The timeout for contacting the RADIUS server, in seconds. * Optional, defaults to 5 seconds. */ 'timeout' => 5, /* * The number of times we should retry connections to the RADIUS server. * Please note that retries would be attempted with each server before * trying with the next server in the queue, so if you want not to wait * before trying the next server, retries should be set to 1. * Optional, defaults to 3 attempts. */ 'retries' => 3, /* * The NAS identifier to use when querying the radius server. * Optional, defaults to the current host name. */ 'nas_identifier' => 'client.example.org', /* * The attribute name we should store the username in. Ths username * will not be saved in any attribute if this is NULL. * Optional, defaults to NULL. */ 'username_attribute' => 'eduPersonPrincipalName', ), User attributes --------------- If the RADIUS server is configured to include attributes for the user in the response, this module may be able to extract them. This requires the attributes to be stored in a vendor-specific attribute in the response from the RADIUS server. The code expects one vendor-attribute with a specific vendor and a specific vendor attribute type for each user attribute. The vendor-attribute must contain a value on the form =. The following configuration options are available for user attributes: /* * This is the vendor for the vendor-specific attribute which contains * the attributes for this user. This can be NULL if no attributes are * included in the response. * Optional, defaults to NULL. */ 'attribute_vendor' => 23735, /* * The vendor attribute-type of the attribute which contains the * attributes for the user. * Required if 'vendor' is set. */ 'attribute_vendor_type' => 4,