Hugh Irvine hugh at open.com.au
Fri Nov 28 16:40:44 CST 2008

Hello Eddie -

I'm not sure I understand your question.

Radiator is normally configured to process RADIUS requests and perform  
authentication against a list of usernames and passwords stored in  
some form of database.

The user database can be LDAP, SQL, flat files, or whatever.

If you want Radiator to query an LDAP database you should use the  
AuthBy LDAP2 clause.

See "goodies/ldap.cfg" and section 5.36 in the Radiator 4.3.1  
reference manual ("doc/ref.pdf").



On 29 Nov 2008, at 01:18, Eddie Chu wrote:

> Dear Sir,
> 	Our application supports LDAP only, is there any way to route /
> bridge / proxy LDAP to RADIUS server.
> Best Rgds,
> Eddie Chu
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
CATool: Private Certificate Authority for Unix and Unix-like systems.

More information about the radiator mailing list