Package com.theorem.radius3.dmcoaclient

Client side Disconnect-Message and Change-of-Authorization messages support.

See:
Description

Interface Summary

DMCOACallback

Interface to use when handling a Disconnect-Message or Change-of-Authorization Message.

Class Summary

DMCOAReceiver	Class to act as a DM / COA RADIUS packet receiver.
DMCOAResponse	Packet information to be returned to the requesting server.

Package com.theorem.radius3.dmcoaclient Description

Client side Disconnect-Message and Change-of-Authorization messages support. DM & COA messages are sent from the server to compliant clients to force disconnects and session authorization attributes respectively. The details are found in RFC 3576 'Dynamic Authorization Extensions to RADIUS'.

The client side provides a mini-server that waits for DM/COA packets and uses a callback mechanism to inform the program that a packet has been received.

The DMCOA receiver may handle DMCOA requests for multiple clients. The DMCOACallback class should be informed of all identifier information detailed in RFC 3576 (Dynamic Authorization Extensions to RADIUS) for each client and use this information to modify the session accordingly on the reception of the callback. The DMCOACallback will present all identity attributes the server sends.

Here is an example of how to use the DMCOAClient.

	public classDMCOATest implements DMCOACallback
	...
	DMCOAReceiver dr;
	// Start the independent receiver.
	// radiusServer is the RADIUS server's address.
	// secret is the shared secret.
	// debug is a boolean indicator that we require debugging information.
	// The 0 indicates use the default DMCOA port.
	// 'this' is the class that implements the DMCOACallback class.
	InetAddress rs = InetAddress.getByName(radiusServer);
	dr = new DMCOAReceiver(rs, Util.toUTF8(secret), debug, 0, this);
	...
	// Stop the DMCOAReceiver.
	dr.stop();