;
> Thank you
> Markus
>
> - Original Message - From: "Hugh Irvine"
> To: "Markus Moeller"
> Cc:
> Sent: Sunday, September 26, 2010 5:36 AM
> Subject: Re: [RADIATOR] (RADIATOR) enable privilege levels for TACACS+ server
>
>
>
> Hel
36 AM
Subject: Re: [RADIATOR] (RADIATOR) enable privilege levels for TACACS+
server
Hello Markus -
We have now added these values into cisco-avpair attributes in the derived
RADIUS request.
This support is in the latest Radiator 4.7 patch set (from today), and the
reference manual will be
t;
> To: "Markus Moeller"
> Cc:
> Sent: Friday, September 24, 2010 11:51 PM
> Subject: Re: [RADIATOR] (RADIATOR) enable privilege levels for TACACS+
> server
>
>
>
> Hello Markus -
>
> You can do this already with the AuthenticationStartHook.
>
&
dling and is not what I want.
Anyway why does this basic TACACS attribute need special treatment ?
Thank you
Markus
- Original Message -
From: "Hugh Irvine"
To: "Markus Moeller"
Cc:
Sent: Friday, September 24, 2010 11:51 PM
Subject: Re: [RADIATOR] (RADIATOR) enable pr
Hello Markus -
Further to this, these values are now passed to the hook in the latest Radiator
4.7 patch set.
regards
Hugh
On 25 Sep 2010, at 08:51, Hugh Irvine wrote:
>
> Hello Markus -
>
> You can do this already with the AuthenticationStartHook.
>
> See the code immediately following
Hello Markus -
You can do this already with the AuthenticationStartHook.
See the code immediately following what you show below.
regards
Hugh
On 25 Sep 2010, at 03:09, Markus Moeller wrote:
> Hi,
>
> Would it be possible to map also the privilege level from the tacacs request
> into a r
Hi,
Would it be possible to map also the privilege level from the tacacs request
into a radius attribute ? This will allow to differentiate in Radiator if a
user typed enable or enable 5 or enable 7.
Thank you
Markus
# Hand
