Feedback
|
Contents
- Attribute Screening for Access Requests
- Finding Feature Information
- Prerequisites for Attribute Screening for Access Requests
- Restrictions for Attribute Screening for Access Requests
- Information About Attribute Screening for Access Requests
- Configuring an NAS to Filter Attributes in Outbound Access Requests
- How to Configure Attribute Screening for Access Requests
- Configuring Attribute Screening for Access Requests
- Configuring a Router to Support Downloadable Filters
- Troubleshooting Tips
- Monitoring and Maintaining Attribute Filtering for Access Requests
- Configuration Examples for Attribute Filtering for Access Requests
- Attribute Filtering for Access Requests Example
- Attribute Filtering User Profile Example
- debug radius Command Example
- Additional References
- Feature Information for Attribute Screening for Access Requests
Attribute Screening for Access Requests
The Attribute Screening for Access Requests feature allows you to configure your network access server (NAS) to filter attributes in outbound Access Requests to the RADIUS server for purposes of authentication or authorization.
- Finding Feature Information
- Prerequisites for Attribute Screening for Access Requests
- Restrictions for Attribute Screening for Access Requests
- Information About Attribute Screening for Access Requests
- How to Configure Attribute Screening for Access Requests
- Configuration Examples for Attribute Filtering for Access Requests
- Additional References
- Feature Information for Attribute Screening for Access Requests
Finding Feature Information
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Attribute Screening for Access Requests
Configuring an NAS to Filter Attributes in Outbound Access Requests
The Attribute Screening for Access Requests feature allows you to configure your NAS to filter attributes in outbound Access Requests to the RADIUS server for purposes of authentication or authorization. The filters can be configured on the NAS, or they can be downloaded via downloadable vendor-specific attributes (VSAs) from the authentication, authorization, and accounting (AAA) server.
The following are some examples of the downloadable VSAs:
Cisco:Cisco-Avpair=âppp-authen-type=chapâ Cisco:Cisco-Avpair=âppp-authen-list=group 1â Cisco:Cisco-Avpair=âppp-author-list=group 1â Cisco:Cisco-Avpair=âvpdn:tunnel-id=B53â Cisco:Cisco-Avpair=âvpdn:ip-addresses=10.0.58.35â
![]() Note | You must be aware of which attributes you want to filter. Filtering certain key attributes can result in authentication failure (for example, attribute 60 should not be filtered). |
How to Configure Attribute Screening for Access Requests
- Configuring Attribute Screening for Access Requests
- Configuring a Router to Support Downloadable Filters
- Monitoring and Maintaining Attribute Filtering for Access Requests
Configuring Attribute Screening for Access Requests
- authorization [request | reply][accept | reject] listname
- accounting [request | reply] [accept | reject] listname
DETAILED STEPS
Configuring a Router to Support Downloadable Filters
DETAILED STEPS
Monitoring and Maintaining Attribute Filtering for Access Requests
DETAILED STEPS
Configuration Examples for Attribute Filtering for Access Requests
- Attribute Filtering for Access Requests Example
- Attribute Filtering User Profile Example
- debug radius Command Example
Attribute Filtering for Access Requests Example
The following example shows that the attributes 30-31 that are defined in âall-attrâ will be rejected in all outbound Access Request messages:
aaa group server radius ras server 172.19.192.238 auth-port 1745 acct-port 1746 authorization request reject all-attr ! . . . radius-server attribute list all-attr attribute 30-31 ! . . .
Attribute Filtering User Profile Example
The following is a sample user profile after attribute filtering has been configured for Access Requests:
cisco.com Password = "cisco" Service-Type = Framed, Framed-Protocol = PPP, Cisco:Cisco-Avpair = :1:"rad-serv=172.19.192.87 key rad123", Cisco:Cisco-Avpair = :1:"rad-serv-filter=authorization request reject range1", Cisco:Cisco-Avpair = :1:"rad-serv-filter=accounting request reject range1", Cisco:Cisco-Avpair = "ppp-authen-type=chap" Cisco:Cisco-Avpair = "ppp-authen-list=group 1", Cisco:Cisco-Avpair = "ppp-author-list=group 1", Cisco:Cisco-Avpair = "ppp-acct-list=start-stop group 1", Cisco:Cisco-Avpair = "vpdn:tunnel-id=B53", Cisco:Cisco-Avpair = "vpdn:tunnel-type=l2tp", Cisco:Cisco-Avpair = "vpdn:ip-addresses=10.0.58.35", Cisco:Cisco-Avpair = "vpdn:l2tp-tunnel-password=cisco" user2@cisco.com Service-Type = Outbound, Cisco:Cisco-Avpair = "vpdn:tunnel-id=B53", Cisco:Cisco-Avpair = "vpdn:tunnel-type=l2tp", Cisco:Cisco-Avpair = "vpdn:ip-addresses=10.0.58.35", Cisco:Cisco-Avpair = "vpdn:l2tp-tunnel-password=cisco"
When a session for user2@cisco.com âcomes upâ at the Layer 2 Tunneling Protocol (L2TP) Network Server (LNS)--as is shown above--because the aaa authorization template command has been configured, a RADIUS request is sent to the server for Cisco.com. The server then sends an Access Accept message if authentication is successful, along with the VSAs that are configured as part of the Cisco.com profile. If filters are configured as part of the Cisco.com profile, these filters will be parsed and applied to the RADIUS requests for user2@cisco.com.
In the above profile example, filter range1 has been applied to the authorization and accounting requests.
debug radius Command Example
If the attribute you are trying to filter is rejected, you will see an debug radius output statement similar to the following:
RADIUS: attribute 31 rejected
If you try to filter an attribute that cannot be filtered, you will see an output statement similar to the following:
RADIUS: attribute 1 cannot be rejected
Additional References
Related Documents
MIBs
Technical Assistance
|
Description |
Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for Attribute Screening for Access Requests
The following table provides release information about the feature or features described in this module. This table 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.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Attribute Screening for Access Requests |
Cisco IOS XE Release 2.1 |
This feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. The Attribute Screening for Access Requests feature allows a network access server (NAS) to be configured to filter attributes in outbound Access Requests to the RADIUS server for purposes of authentication or authorization. The following commands were introduced or modified by this feature: authorization (server-group). |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Feedback