Adding Vendor Specific Attribute to the Access-Accept

[normal ozone]

Sorry for the late reply.

I found the reason why the attributes I added where not
included in the reply list. Those attributes are used by the servers internally 
(Range:  1000-1199)
They do not go to the reply attributes list.

When I tried the attributes from other vendors like 3Com it worked. 
The reply attributes were included in the Access-Accept message.

My new question is can you suggest an attribute that I can use to internally 
control
access to features in my application? I planned to use User-Category and define
a list of categories that can only access certain features. But since this is 
not listed
in the reply attributes list I cannot use it.

Regards,




________________________________
From: Josip Almasi <joe at vrspace.org>
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
Sent: Thu, April 28, 2011 8:28:10 PM
Subject: Re: Adding Vendor Specific Attribute to the Access-Accept

normal ozone wrote:
> Hello,
> 
> I want to be able to receive the Vendor Specific Attribute that I set in a 
>user.
> For example I added the following attribute to my user using daloradius:
>  Vendor: dictionary.freeradius.internal
>  Attribute: User-Category
>  Value: MyCategory

Better check dictionary file.

> In the Oreilly Manual it mentions that Access-Accept can send Optional 
>attributes.
> Is there a way to setup freeradius so that this attribute can be included in 
>the Access-Accept message?

Sure, just add them to users file, same as any other attributes.
FR will complain if you add some attributes which are not in the dictionary.

> By the way I'm using the installer version of freeradius for my radius server. 
>And my radius client
> is also a pc (I use a java library named TinyRadius)

I use TiniRadius too, mighty fine.

Regards...

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110501/c1f6cadc/attachment.html>