<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NAF NAP problem in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/naf-nap-problem/m-p/890570#M407909</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Network access restrictions (NARs) provide authorization conditions that have to be met before a user can gain access to the network. Cisco Secure Access Control Server (ACS) applies these conditions using information from attributes sent by authentication, authorization, and accounting (AAA) clients. Although you may set up NARs in several ways, they all are based on matching attribute information sent by a AAA client. Therefore, you must understand the format and content of the attributes that your AAA clients send if you want to employ NARs effectively. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Jan 2008 15:11:59 GMT</pubDate>
    <dc:creator>jbayuka</dc:creator>
    <dc:date>2008-01-28T15:11:59Z</dc:date>
    <item>
      <title>NAF NAP problem</title>
      <link>https://community.cisco.com/t5/network-access-control/naf-nap-problem/m-p/890569#M407908</link>
      <description>&lt;P&gt;HiWe use a VPN-Router for SSL-VPN,ACS4.1 and for the OWA-Users the LDAP database. The problem i have is that i want to define that only the Users with SSL-VPN are forwarded to the LDAP. This is possible with NAPs and NAFs but there is my problem: Every NAS that is configured as RADIUS is no disabled, because there is no profile that mached. It seems that the NAF definition in the NAP doesn't work. Can you help me??&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 22:36:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/naf-nap-problem/m-p/890569#M407908</guid>
      <dc:creator>dbelno</dc:creator>
      <dc:date>2019-03-10T22:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: NAF NAP problem</title>
      <link>https://community.cisco.com/t5/network-access-control/naf-nap-problem/m-p/890570#M407909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Network access restrictions (NARs) provide authorization conditions that have to be met before a user can gain access to the network. Cisco Secure Access Control Server (ACS) applies these conditions using information from attributes sent by authentication, authorization, and accounting (AAA) clients. Although you may set up NARs in several ways, they all are based on matching attribute information sent by a AAA client. Therefore, you must understand the format and content of the attributes that your AAA clients send if you want to employ NARs effectively. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jan 2008 15:11:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/naf-nap-problem/m-p/890570#M407909</guid>
      <dc:creator>jbayuka</dc:creator>
      <dc:date>2008-01-28T15:11:59Z</dc:date>
    </item>
  </channel>
</rss>

