<?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: Multiple identity sources for Authorization in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4548149#M572659</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97757"&gt;@mletchworth&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;As &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/388087"&gt;@Greg Gibbs&lt;/a&gt; wrote, such flow is not possible. ISE can either process authentication on its own, or it can pass it forward to someone else, but can still proceed with authorization.&lt;/P&gt;
&lt;P&gt;How I did implementations with Duo is to install Duo Authentication Proxy, to integrate it with AD/LDAP and Duo cloud, and then to integrate ISE with Duo Proxy via RADIUS protocol. Guide that Greg shared is by using External RADIUS servers. I also used integration with ISE as RADIUS Token server.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Milos&lt;/P&gt;</description>
    <pubDate>Wed, 09 Feb 2022 07:15:38 GMT</pubDate>
    <dc:creator>Milos_Jovanovic</dc:creator>
    <dc:date>2022-02-09T07:15:38Z</dc:date>
    <item>
      <title>Multiple identity sources for Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4547156#M572636</link>
      <description>&lt;P&gt;Is it possible to require authorization against two external identity sources? Identity source sequence seems to only require passing one or the other external identity source, but want to require both. I would like to use LDAP to valid the user (verify password and group membership "this has been working fine") then after that is validated, send the username and password to our DUO radius proxy for MFA (Duo-Client-Only) processing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use ISE to authorize remote VPN users on our ASA. We now have a requirement to add MFA push at login.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2022 06:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4547156#M572636</guid>
      <dc:creator>mletchworth</dc:creator>
      <dc:date>2022-02-08T06:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple identity sources for Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4547867#M572657</link>
      <description>&lt;P&gt;That type of authentication flow is not possible. The way to implement Duo MFA with ISE is using the Duo Authentication Proxy and having it do the lookup against LDAP as documented in &lt;A href="https://duo.com/docs/ciscoise-radius" target="_blank" rel="noopener"&gt;this Duo guide&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2022 21:29:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4547867#M572657</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2022-02-08T21:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple identity sources for Authorization</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4548149#M572659</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97757"&gt;@mletchworth&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;As &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/388087"&gt;@Greg Gibbs&lt;/a&gt; wrote, such flow is not possible. ISE can either process authentication on its own, or it can pass it forward to someone else, but can still proceed with authorization.&lt;/P&gt;
&lt;P&gt;How I did implementations with Duo is to install Duo Authentication Proxy, to integrate it with AD/LDAP and Duo cloud, and then to integrate ISE with Duo Proxy via RADIUS protocol. Guide that Greg shared is by using External RADIUS servers. I also used integration with ISE as RADIUS Token server.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Wed, 09 Feb 2022 07:15:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-identity-sources-for-authorization/m-p/4548149#M572659</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2022-02-09T07:15:38Z</dc:date>
    </item>
  </channel>
</rss>

