Radius Server Programming Guide

RADIUS Server API Programming Guide

Release Notes and Bug Fixes

New Features

Bug Fixes

Contacting Customer Support

Preface

License Agreement

Related Requests For Comment (RFCs)

Overview

Overview of Features

How RADIUS Servers Work

RADIUS API Directory Structure

Platforms Supported

Installing the RADIUS API

Installing on a LINUX/UNIX Host

Installing on Windows

Getting Started

Server Quick Start

Logging

Authentication

PAP

CHAP

MS-CHAP & MS-CHAP 2

EAP & EAP-MD5

EAP-LEAP (Lightweight EAP)

Digest Authentication

EAP-TLS

Accounting

Proxy Services - Built in

Proxy Interception

NAS Interception

SNMP

Extended RADIUS Packet Types

Disconnect & Change of Authorization Messages

Server API Methods

Encryption

Issues running the server

Configuring the Server API

The RADIUSServer Methods

Log Files and Logging

Special Classes

Attribute

AttributeList

RADIUSClient & (JAAS) LoginModule

VendorSpecific

Internal Server Details

Duplicate packet checking

State Attribute Associations

Proxy-State Associations

Requests For Comment (RFC's)

These RFC have been implemented in the server (and client were applicable). Implemented means that the RFC's are supported functionally but not in policy. For example an attribute may require some action based on context. The server only knows about the attribute but does make any decisions because that is the responsiblity of the local programmer.