So the answer is (apparently) that the ID ("vendor type" in RFC 2865) doesn't matter. The switch only looks at the vendor ID (maybe) and the contents of the VSA value (string).
Of course, this fact isn't documented anywhere, so I'm not sure how people setting up RADIUS servers are supposed to know what value to use for the vendor type.
The good news is that this does work, once one creates an authorization method list and adds it to the terminal lines. Too bad this isn't mentioned here.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
NoOneOfConsequence
1 Rookie
•
28 Posts
0
April 26th, 2019 17:00
So the answer is (apparently) that the ID ("vendor type" in RFC 2865) doesn't matter. The switch only looks at the vendor ID (maybe) and the contents of the VSA value (string).
Of course, this fact isn't documented anywhere, so I'm not sure how people setting up RADIUS servers are supposed to know what value to use for the vendor type.
The good news is that this does work, once one creates an authorization method list and adds it to the terminal lines. Too bad this isn't mentioned here.
<ADMIN NOTE: Broken link has been removed from this post by Dell>