Filter
Top Products
5-7
Installing and Configuring Cisco Access Registrar, 4.2
OL-17221-02
Chapter 5 Customizing Your Configuration
Configuring Multiple UserLists
In this situation, when beth@North.QuickExample.com makes an Access-Request, the script will strip off
the word
North and use it to set the value of the environment variable Authentication-Service and/or
Authorization-Service. Note, the script overrides any existing default authentication and/or
authorization specifications.
Note For more information about writing scripts and the role the dictionaries play in Cisco AR,
see the Cisco Access Registrar User Guide. For examples of scripts, see the Cisco Access
Registrar User’s Guide.
Client Scripting
Though, CAR allows external code (Tcl/C/C++/Java) to be used by means of a script, custom service,
policy engine, and so forth, while processing request, response, or while working with the environment
dictionaries, it shall not be responsible for the scripts used and will not be liable for any direct, indirect,
incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of
substitute goods or services; loss of use, data, or profits; or business interruption) however caused and
on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise)
arising in any way out of the use of the script.
Configuring the Script
When you have multiple UserLists, you need a script to determine which UserList to check when a user
makes an Access-Request. When you want the script to apply to all users, irrespective of the NAS they
are using, place the script at the Radius level. When, on the other hand, you want to run different scripts
depending on the originating NAS, place the script at the Client level.
Client Scripting
Though, CAR allows external code (Tcl/C/C++/Java) to be used by means of a script, custom service,
policy engine, and so forth, while processing request, response, or while working with the environment
dictionaries, it shall not be responsible for the scripts used and will not be liable for any direct, indirect,
incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of
substitute goods or services; loss of use, data, or profits; or business interruption) however caused and
on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise)
arising in any way out of the use of the script.
Choosing the Scripting Point
Step 1 Use the cd command to change to the appropriate level. The following example sets the script for all
requests.
cd /Radius
Step 2 Use the set command to set the incoming script. The following example sets the script, ParseUserName:
set IncomingScript ParseUserName