Hello Troy,
On Thu, 21 Aug 2003 12:25 am, Troy Holder wrote: > Do I understand the new TACAS support correctly? If you have Radiator > accepting TACAS requests, it basically converts the TACAS request into a > RADIUS request. Then RADIATOR handles the RADIUS request and converts > the RADIUS response into a TACAS response. Correct. > > I use a lot of handlers in my config to deal with different pieces of > equipment needing different return values or different auth schemes. > What kind of info is passed in the RADIUS request that is converted from > a TACAS request? There is not much available from Tacacs+ at authentication time, but you do get: User-Name User-Password Calling-Station-Id (sent as rem_addr by TACACS+) NAS-Port-Id (sent as port by TACACS+) Service-Type (sent as service by TACACS+) Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP etc on Unix, Windows, MacOS etc. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
