Hello John, 'lo Jeremy -
On Thu, 01 Jun 2000, John Hough wrote:
> Hugh,
>
> Back several months ago we had this same discussion and I passed our
> emails on to Jeremy (He works for me). Our configuration has several
> hundred realms on a centralized Radius server, we support local
> authentication via flat file and proxying the radius request to remote
> servers for some of our dealers. In this scenario would your
> recommendation still apply or is it back to the <Client ...> tag as in the
> emails that we had discussed this. Being able to support several
> different NAS devices is appealing to us, especially if we can provide
> support for their Vendor attributes as needed based on where the request
> is coming from..
>
If you want to return different attributes to different types of NAS equipment,
then using the Client Identifier tag is a good way of doing it. As mentioned
previously, the example getProfile/replaceProfile hooks were developed for a
specific purpose, and that was to translate a per-user symbolic Profile name to
a per-NAS-specific set of attributes.
In your scenario above, it is not clear to me how you intend to supply the
per-user Profile name if you want to use the example hooks directly. And in any
case, it may very well be that you will need to come up with a different
approach and develop hooks of your own to address your own requirements.
Perhaps you can clarify your requirements?
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
