<?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: ISE Aruba integration issues in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3859522#M472860</link>
    <description>There could be a couple things going on but most of the time it is the result of the RADIUS AV pairs not matching the correct authorization rule in your policy.  You will have to modify your authorization rule so that it matches the RADIUS AV information coming from Aruba.  Otherwise, you will continue to match the default authorization rule.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;-Tim</description>
    <pubDate>Mon, 20 May 2019 16:42:35 GMT</pubDate>
    <dc:creator>Timothy Abbott</dc:creator>
    <dc:date>2019-05-20T16:42:35Z</dc:date>
    <item>
      <title>ISE Aruba integration issues</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3859432#M472855</link>
      <description>&lt;PRE&gt;&lt;SPAN&gt;The integration of ISE with Aruba is being carried out.
ISE is in version 2.2 and is being integrated with an IAP that is in 8.5
The configuration was done by guiding us with the following document, where each step is explained well.&lt;BR /&gt;&lt;BR /&gt;https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-20/211406-Configure-Guest-Flow-with-ISE-2-0-and-Ar.pdf&lt;BR /&gt;&lt;BR /&gt;
At the moment of doing the test it is evidenced in the ISE logs of events of the Aruba device but the traffic sends it to the default policy.
How can we validate what happens or what could be modified in the configuration?&lt;/SPAN&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 20 May 2019 14:44:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3859432#M472855</guid>
      <dc:creator>cnogueral</dc:creator>
      <dc:date>2019-05-20T14:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Aruba integration issues</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3859522#M472860</link>
      <description>There could be a couple things going on but most of the time it is the result of the RADIUS AV pairs not matching the correct authorization rule in your policy.  You will have to modify your authorization rule so that it matches the RADIUS AV information coming from Aruba.  Otherwise, you will continue to match the default authorization rule.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;-Tim</description>
      <pubDate>Mon, 20 May 2019 16:42:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3859522#M472860</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-05-20T16:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Aruba integration issues</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3861145#M472862</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;According to the configuration recommended in the guide, this should work. Some changes have been made but it's still the same error
May it have to see with the model and the firmware version of the Aruba IAP?
For this type of integration, i could open a case with the Cisco TAC, or because it is with another manufacturer Cisco does not support?&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;/SPAN&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 22 May 2019 19:29:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-aruba-integration-issues/m-p/3861145#M472862</guid>
      <dc:creator>cnogueral</dc:creator>
      <dc:date>2019-05-22T19:29:51Z</dc:date>
    </item>
  </channel>
</rss>

