redundancy/failover support for LDAP xlat
Dear FreeRADIUS users, I am working on setting up LDAP failover for my radius servers. I currently have two instances defined in the modules section: ldap ldap1 {...} ldap ldap2 {...} and have a redundant section in authorize: redundant { ldap1 ldap2 } This is correctly making the connection to the ldap server. However, in the users file I am using the ldap_xlat process to send the appropriate Class definition back to the network gear: DEFAULT Auth-Type = Kerberos, NAS-IP-Address == x.y.z.g Class = "OU=%{ldap:ldap:///dc=rice,dc=edu?Class?sub?uid=%u}" The problem is that that this does not work unless I define a specific instance for the xlat process. This does not allow it to failover to the working server. Does anyone have any ideas about how to implement such functionality? Ken Marshall
Kenneth Marshall wrote: ...
DEFAULT Auth-Type = Kerberos, NAS-IP-Address == x.y.z.g Class = "OU=%{ldap:ldap:///dc=rice,dc=edu?Class?sub?uid=%u}"
The problem is that that this does not work unless I define a specific instance for the xlat process. This does not allow it to failover to the working server. Does anyone have any ideas about how to implement such functionality?
Nope. If you can find a good way to do this, I'd love to know. It's an open problem. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Kenneth Marshall