Title: Message

It sounds like you have the setting ‘RadiusAttributeMode’ defined in your sproxy.conf file. With this enabled you are telling slipstream to allow logins from profiles with a specific attribute (of your choosing) present.

 

I don’t use this setting and it is commented out. This leaves me with standard Radius authentication.

 

It is my understanding that leaving the ‘RadiusAttributeMode’ undefined or set to false makes sproxy ignore the ‘RadiusAttributeID & RadiusAttributeValue’  settings …. Which seems to be the cause of your issue.

 

Brad Johnson

  Systems Administrator

    Local Link Network Operations

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 10:51 AM
To: [EMAIL PROTECTED]
Subject: [VOPRadius] Need help with new Slipstream requirement

 

Hi,

Is anyone here using Slipstream with Vircom Radius?
We are updating the slipstream server and it is asking for a vendor specific
attribute.
Vircom has no clue what to put in there.
Slipstream does not know either.

The following is the information that Slipstream is requiring....

-----------------------------------------
Setting Name : RadiusAttributeID
Mandatory : no
Default Value : none
Valid Values : An integer between 0 and 2^31 - 1 (inclusive)

When RADIUS attribute mode is enabled, the vender-specific attribute in the
"Access-Accept" packet must have a vendor ID equal to the 'RadiusVendorID'
and an attribute ID equal to this setting.
-------------------------------------------

Will Merrill
The Kingdom Connection

Reply via email to