Proxy-State support in 2.x?

Dale E. Reed Jr. (daler@iea.com)
Sun, 22 Jun 1997 12:22:37 -0700

My preliminary tests show that Livington's 2.0 RADIUS server (UNIX) is
not returning the Proxy-State attribute as required by the RFC (MUST):

> 5.33. Proxy-State
>
> Description
>
> This Attribute is available to be sent by a proxy server to
> another server when forwarding an Access-Request and MUST be
> returned unmodified in the Access-Accept, Access-Reject or
> Access-Challenge. This attribute should be removed by the proxy
> server before the response is forwarded to the NAS.
>
> Usage of the Proxy-State Attribute is implementation dependent. A
> description of its function is outside the scope of this
> specification.

We are testing out Proxy capabilities, and one of the main uses of it is
to have RadiusNT on the front end with the ability to proxy requests
to several backend servers, including Livingston. Since we require the
Proxy-State to be returned to match the requests up, if the server does
not return this, proxying does not work.

Has anyone pathced 2.0 for proxy-state support and has Livingston
addressed this in 2.01? I honestly haven't had a chance to look at
2.01, and the release notes don't mention anything about it.

-- 
Dale E. Reed Jr.  (daler@iea.com)
_________________________________________________________________
       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs
 Internet Solutions for Today  |    http://www.emerald.iea.com