The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Local AAA Server feature allows you to configure your router so that user authentication and authorization attributes currently available on AAA servers are available locally on the router. The attributes can be added to existing framework, such as the local user database or subscriber profile. The local AAA server provides access to the complete dictionary of Cisco IOS XE supported attributes.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Local AAA Server" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
•Prerequisites for Local AAA Server
•Information About Local AAA Server
•How to Configure Local AAA Server
•Configuration Examples for Local AAA Server
•Feature Information for Local AAA Server
The aaa new-model command must be issued in global configuration mode to enable AAA services before using this feature.
•Local Authorization Attributes: Overview
The AAA subsystem (authentication, authorization, and accounting) is responsible for managing all supported attributes that are available to the various services within the Cisco IOS XE software. As such, it maintains its own local dictionary of all supported attributes.
You can configure your router so that AAA authentication and authorization attributes currently available on AAA servers are made available on existing Cisco IOS XE devices. The attributes can be added to existing framework, such as the local user database or subscriber profile. For example, an attribute list can now be added to an existing username, providing the ability for the local user database to act as a local AAA server. For situations in which the local username list is relatively small, this flexibility allows you to provide complete user authentication or authorization locally within the Cisco IOS XE software without having a AAA server. This ability can allow you to maintain your user database locally or provide a failover local mechanism without having to sacrifice policy options when defining local users.
A subscriber profile allows domain-based clients to have policy applied at the end-user service level. This flexibility allows common policy to be set for all users under a domain in one place and applied there whether or not user authorization is done locally. An attribute list can be added to the subscriber profile, allowing the profile to apply all attributes that can be applied to services using AAA servers. Attributes that are configured under the AAA attribute list are merged with the existing attributes that are generated with the existing subscriber profile and passed to the Subscriber Server Switch (SSS) framework for application.
Note Accounting is still done on a AAA server and is not supported by this feature.
AAA attribute lists define user profiles that are local to the router. Every attribute that is known to the AAA subsystem is made available for configuration.
The AAA attributes that are defined in the AAA attribute list are standard RADIUS or TACACS+ attributes. However, they are in the Cisco IOS XE internal format for that attribute. The attributes must be converted from the RADIUS format (for a RADIUS case) to the Cisco IOS XE AAA interface format. TACACS+ attributes are generally identical to the Cisco IOS XE AAA interface format.
You can use the show aaa attributes protocol radius command to get the Cisco IOS XE AAA format of the Internet Engineering Task Force (IETF) RADIUS attribute. The show command output provides a complete list of all the AAA attributes that are supported.
Note The conversion from RADIUS to internal AAA is done internally within the AAA framework. RADIUS vendor-specific attributes (VSAs) are usually accurately reflected during conversion. TACACS+ attributes are also usually identical to the local attributes and do not require the conversion process. However, IETF numbered attributes and some special VSAs often require the conversion process.
Attributes are not validated at configuration. The AAA subsystem "knows" only the format that is expected by the services when the service defines a given attribute inside a definition file. However, it cannot validate the attribute information itself. This validation is done by a service when it first uses the attribute. This validation applies whether the AAA server is RADIUS or TACACS+. Thus, if you are not familiar with configuring a AAA server, it is advisable that you test your attribute list on a test device with the service that will be using the list before configuring and using it in a production environment.
This section contains the following procedures:
•Defining a AAA Attribute List (required)
•Defining a Subscriber Profile (required)
•Monitoring and Troubleshooting a Local AAA Server (optional)
To define an AAA attribute list, perform the following steps.
1. enable
2. configure terminal
3. aaa attribute list list-name
4. attribute type {name} {value} [service service] [protocol protocol]
5. attribute type {name} {value} [service service] [protocol protocol]
6. attribute type {name} {value} [service service] [protocol protocol]
7. attribute type {name} {value}
8. attribute type {name} {value}
9. attribute type {name} {value}
To define a subscriber profile, perform the following steps.
Note RADIUS users should use the show aaa attributes command to map the RADIUS version of the particular attribute to the Cisco IOS XE AAA version of the string attribute. See the example "Mapping from the RADIUS Version of a Particular Attribute to the Cisco IOS XE AAA Version: Example."
1. enable
2. configure terminal
3. subscriber authorization enable
4. policy-map type service domain-name
5. service local
6. exit
7. aaa attribute list list-name
The following debug commands may be helpful in monitoring and troubleshooting, especially to ensure that domain-based service authorization is being triggered and that location authorization is being called on the local AAA server, which triggers the service.
1. enable
2. debug aaa authentication
3. debug aaa authorization
4. debug aaa per-user
5. debug ppp authentication
6. debug ppp error
7. debug ppp forward
8. debug ppp negotiation
9. debug radius
10. debug sss error
This section contains the following configuration examples:
•Mapping from the RADIUS Version of a Particular Attribute to the Cisco IOS XE AAA Version: Example
The following example shows a Point to Point over Ethernet (PPPoE) group named "bba-group" that is configured for subscriber profile cisco.com (thus, any user with the domain name cisco.com will execute the subscriber profile cisco.com authorization policy). The cisco.com subscriber profile is configured to attach the AAA attribute list "TEST," which has both "ip vrf forwarding" and "ip unnumbered" configured for PPP service under Link Control Protocol (LCP) negotiation. This configuration will essentially cause the named attributes to be applied on the session with the cisco.com domain under the bba-group "pppoe grp1."
aaa authentication ppp template1 local
aaa authorization network template1 local
!
aaa attribute list TEST
attribute type interface-config "ip unnumbered Loopback0" service ppp protocol lcp
attribute type interface-config "ip vrf forwarding blue" service ppp protocol lcp
!
ip vrf blue
description vrf blue template1
rd 1:1
route-target export 1:1
route-target import 1:1
!
subscriber authorization enable
!
policy-map type service example.com
service local
aaa attribute list TEST
!
bba-group pppoe grp1
virtual-template 1
service profile example.com
!
interface Virtual-Template1
no ip address
no snmp trap link-status
no peer default ip address
no keepalive
ppp authentication pap template1
ppp authorization template1
!
Note In some versions of Cisco IOS XE software, it is better to use the explicit attribute instead of interface- configuration because it provides better scalability (full VAccess interfaces are not required, and sub interfaces could be used to provide the service). In such a case, you might configure "attribute type ip-unnumbered `Loopback0' service ppp protocol ip" instead of "attribute type interface-config `ip unnumbered Loopback0' service ppp protocol lcp."
The following output example of the show aaa attributes command lists RADIUS attributes, which can be used when configuring this feature.
Router# show aaa attributes protocol radius
IETF defined attributes:
Type=4 Name=acl Format=Ulong
Protocol:RADIUS
Unknown Type=11 Name=Filter-Id Format=Binary
Converts attribute 11 (Filter-Id) of type Binary into an internal attribute
named "acl" of type Ulong. As such, one can configure this attributes locally
by using the attribute type "acl."
Cisco VSA attributes:
Type=157 Name=interface-config Format=String
Simply expects a string for the attribute of type "interface-config."
Note The aaa attribute list command requires the Cisco IOS XE AAA version of an attribute, which is defined in the "Name" field above.
|
|
---|---|
Cisco IOS commands |
|
Security commands |
|
|
---|---|
None. |
— |
|
|
---|---|
None. |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
|
|
---|---|
None. |
— |
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.