<?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 Sure, we commonly use EAP in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-policy-set-machine-user/m-p/2671377#M55346</link>
    <description>&lt;P&gt;Sure, we commonly use EAP chaining to address this use case. Please see "&lt;A href="http://www.cisco.com/c/dam/en/us/td/docs/security/ise/how_to/HowTo-82_Deploy_EAP_Chaining.pdf" style="color: rgb(102, 51, 153); font-family: arial, helvetica, sans-serif; font-size: 11px; line-height: normal;" target="_blank"&gt;HowTo: EAP Chaining Deployment Configurations&lt;/A&gt;" on the ISE Design Guide page.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Specifically see the section beginning on page 15 which describes:&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;In this example, these rules will be defined based on the EAP-Chaining results:&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• If both user and machine both succeeded&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• If user succeeded and machine failed&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• No chaining is supported&lt;/P&gt;</description>
    <pubDate>Sun, 31 May 2015 17:39:49 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2015-05-31T17:39:49Z</dc:date>
    <item>
      <title>ISE policy set (Machine+user)</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-set-machine-user/m-p/2671376#M55345</link>
      <description>&lt;P&gt;Is there any way to create authorization rule that combine both machine and user identity groups in one rule?&lt;/P&gt;&lt;P&gt;for example, authorization profile match only if computer in external identity X and username in external identity group Y.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:46:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-set-machine-user/m-p/2671376#M55345</guid>
      <dc:creator>ibrahim_hassan</dc:creator>
      <dc:date>2019-03-11T05:46:02Z</dc:date>
    </item>
    <item>
      <title>Sure, we commonly use EAP</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-policy-set-machine-user/m-p/2671377#M55346</link>
      <description>&lt;P&gt;Sure, we commonly use EAP chaining to address this use case. Please see "&lt;A href="http://www.cisco.com/c/dam/en/us/td/docs/security/ise/how_to/HowTo-82_Deploy_EAP_Chaining.pdf" style="color: rgb(102, 51, 153); font-family: arial, helvetica, sans-serif; font-size: 11px; line-height: normal;" target="_blank"&gt;HowTo: EAP Chaining Deployment Configurations&lt;/A&gt;" on the ISE Design Guide page.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Specifically see the section beginning on page 15 which describes:&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;In this example, these rules will be defined based on the EAP-Chaining results:&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• If both user and machine both succeeded&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• If user succeeded and machine failed&lt;/P&gt;&lt;P style="margin-left: 80px;"&gt;• No chaining is supported&lt;/P&gt;</description>
      <pubDate>Sun, 31 May 2015 17:39:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-policy-set-machine-user/m-p/2671377#M55346</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-05-31T17:39:49Z</dc:date>
    </item>
  </channel>
</rss>

