(RADIATOR) Default AuthLOG for all <Handler>'s

[Mahesh Neelakanta]

Thanks Hugh. This is what we started doing. However, having to put the
"AuthLog SQLAuthLog" into each handler would be too much (we have over
1000) to do by hand. What I was hoping for is a "global" AuthLog entry
which would do it for all handlers, etc.
 
mahesh

	-----Original Message-----
	From: Hugh Irvine [mailto:hugh at open.com.au] 
	Sent: Wednesday, August 20, 2003 10:24 PM
	To: Mahesh Neelakanta
	Cc: radiator at open.com.au
	Subject: Re: (RADIATOR) Default AuthLOG for all <Handler>'s
	
	


	Hello Mahesh - 

	You can use an Identifier in your AuthLog clause, then refer to
it as follows: 

	<AuthLog SQL> 
	Identifier SQLAuthLog 
	..... 
	</AuthLog> 

	<Handler ....> 
	..... 
	AuthLog SQLAuthLog 
	..... 
	</Handler> 

	See section 6.49 in the Radiator 3.6 reference manual
("doc/ref.html"). 

	NB - this same technique can also be used with AuthBy clauses,
SessionDatabase clauses, etc. 

	regards 

	Hugh 


	On Wednesday, Aug 20, 2003, at 23:51 Australia/Melbourne, Mahesh
Neelakanta wrote: 


		Is there a way to enable all handlers to use a single
AuthLOG? I.e. we have many, many handlers and need to log
success/failures to find out if we are failing authentications. However,
we want to avoid having to code this into each handler. 
		thanks, 
		mahesh 
		ps. quick & dirty fixes are accepted :-) 



	NB: have you included a copy of your configuration file (no
secrets), 
	together with a trace 4 debug showing what is happening? 

	-- 
	Radiator: the most portable, flexible and configurable RADIUS
server 
	anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS
X. 
	- 
	Nets: internetwork inventory and management - graphical,
extensible, 
	flexible with hardware, software, platform and database
independence. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20030820/0ae6c691/attachment.html>