<?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: Opengear device addition to ISE for TACACS profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428292#M568329</link>
    <description>&lt;P&gt;ISE supports standards-based TACACS+ protocol and methods. If you are looking for what TACACS+ attributes ISE needs to return to the Opengear platform via the TACACS Profile, this is defined by the vendor. If this info is not readily available in their support documentation, you might need to contact the Opengear support team to confirm.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 23:18:45 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2021-07-05T23:18:45Z</dc:date>
    <item>
      <title>Opengear device addition to ISE for TACACS profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428103#M568310</link>
      <description>&lt;P&gt;We have an ISE enviornment with version 2.2 patch 15. There is a new requirement for onboarding a Opengear Management (OOB) device for TACACS authentication. What is the attribute value we need to configure for enbaling the TACACS profile in this case.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 14:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428103#M568310</guid>
      <dc:creator>shalinmary74856</dc:creator>
      <dc:date>2021-07-05T14:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: Opengear device addition to ISE for TACACS profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428108#M568311</link>
      <description>&lt;P&gt;If this device not Cisco, i would check the support matrix of ISE 2.2&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 14:25:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428108#M568311</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2021-07-05T14:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Opengear device addition to ISE for TACACS profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428292#M568329</link>
      <description>&lt;P&gt;ISE supports standards-based TACACS+ protocol and methods. If you are looking for what TACACS+ attributes ISE needs to return to the Opengear platform via the TACACS Profile, this is defined by the vendor. If this info is not readily available in their support documentation, you might need to contact the Opengear support team to confirm.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 23:18:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/opengear-device-addition-to-ise-for-tacacs-profiling/m-p/4428292#M568329</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2021-07-05T23:18:45Z</dc:date>
    </item>
  </channel>
</rss>

