[RADIATOR] Radiator evaluation - Authenticate, Authorize LDAP users through Radius server to Network Switch

Hello, 1) I wanted to know How do you authenticate and authorize LDAP server users through Radiator for a network switch. 2)How do you Map Radiator attributes to the LDAP attributes , -I tried configuring LDAP in the radius.config and tried to run the C:\perl\bin\radiusd to test whether

Re: [RADIATOR] Radiator evaluation - Authenticate, Authorize LDAP users through Radius server to Network Switch

Hi Pramod, check out the various ldap*.cfg config files in the goodies directory as a starting point. Radiator connects on the first use, not on startup. You can also use the radpwtst utility to test your Radiator config so be sure its ok before configuring the switch. Also enable trace level 4

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Thanks for the info Mike! Do you know which devices support it? We're mainly interessted in Cisco gear. Best regards, Alex Am 2012-05-29 22:46, schrieb Mike McCauley: RadSec is now an official RFC. -- Forwarded Message -- Subject: [radext] RFC 6614 on Transport Layer

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Hi, sorry, dont have any info on Cisco. There are a 2 compliant implementations mentioned in the RFC. Cheers. On Wednesday, May 30, 2012 09:18:40 AM Alexander Hartmaier wrote: Thanks for the info Mike! Do you know which devices support it? We're mainly interessted in Cisco gear. Best

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Hi, We are pushing it on the Cisco Wireless, ISE and NCS dev teams. AFAIK, there is no Cisco gear (nor other (wireless) vendor) that supports RADSEC. (Please correct me if I'm wrong...) You (and everybody else that want to see RADSEC implemented in their Cisco gear) should nag your Cisco

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Hi, sorry, dont have any info on Cisco. we have been asking Cisco for such support in their kit (switches, wireless, RADIUS platforms)..now that the RFCs are out we have some more leverage. I ask all Cisco customers to ask their local support/sales/SE/tech-track etc about having support in

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Hi, On Wednesday, May 30, 2012 09:46:04 AM Fredrik Pettai wrote: Hi, We are pushing it on the Cisco Wireless, ISE and NCS dev teams. AFAIK, there is no Cisco gear (nor other (wireless) vendor) that supports RADSEC. (Please correct me if I'm wrong...) Some years ago I tested (successfully)

Re: [RADIATOR] Fwd: [radext] RFC 6614 on Transport Layer Security (TLS) Encryption for RADIUS

Hi, Some years ago I tested (successfully) a Lancom L-54g wireless Access Point which implemented RadSec. I dont know if it or equivalent is still available. LANCOM still do such devices last time I looked - we have a very active member of eduroam here in Europe who was involved with that

Re: [RADIATOR] Alvarion 4Motion and Radiator Explicit Mode Integration

On 05/29/2012 06:39 PM, Edgar Espinoza wrote: Thank you both Leigh and Heikki for your responses. Based on the type of attributes send back to Alvarion's ASN, the system determines if you are working in implicit or explicit mode, see below: Thanks for the example. Most of the attributes are

[RADIATOR] Opera PMS integration

Hi all, wondering if anyone has any experience with PMS integration over TCP/IP? From the documentation included it sounds fairly straightforward, but wondering if anyone has hit any stumbling blocks during their implementations? MICROS are convinced that they've never worked with Radiator

Re: [RADIATOR] Opera PMS integration

Hi Michael, The Radiator-Opera integration and interoperation has been tested successfully by Micros-Fidelio Australia. According to correspondence from them, the Radiator interface for Opera has been released: FKT Logo is RRA and the Part Number is 5009-170 Cheers. On Wednesday, May 30,