[RADIATOR] best practice method for not handling a realm

[Hugh Irvine]

Hello Alan -

Something like this:

.....

<Realm abc.com>
	<AuthBy INTERNAL>
		AuthResul ....
		AcctResult ....
		DefaultResult .....
	</AuthBy>
</Realm>

.....

See section 5.48 in the Radiator 4.4 reference manual ("doc/ref.pdf").

You can set the AuthResult, AcctResult and DefaultResult to whatever  
makes sense in your situation.

regards

Hugh


On 5 Oct 2009, at 20:29, Alan Buxey wrote:

> hi,
>
> what is the best practice method for not handing the
> AAA for an authentication/accounting request for a realm?
>
> ie say we have
>
> user at abc.com
>
> do we (very short-hand rather than full config)
>
> <realm abc.com>
> authby file /dev/null
> </realm>
>
> or
>
> <realm abc.com>
> </realm>
>
> or
>
> <realm abc.com>
> AccountingHandled
> </realm>
>
>
> ...or something else??  the docs dont seem to be too clear on how to
> deal with this in a proxy hierarchy - if we dont have a response then
> the downstream think we are dead...and will then hit the alernative  
> proxy
> and fail on that - causing a failure domino ripple and putting the  
> proxy
> out of action for whatever their timeout/alive period is set to.
>
> many thanks
>
> alan
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB:

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:
http://www.open.com.au/wiki/index.php/Main_Page

-- 
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.