<?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 ISE - External Identity Store - Two Factor Request Passes Token and Password in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443715#M539325</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My customer is using ISE for TACACS and would like to enable two factor authentication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They currently have their two factor authentication server configured as an external identity store which works as expected.&amp;nbsp; Problem is, when ISE sends the request to the RADIUS token server for authentication, it sends the AD username/password along with the token.&amp;nbsp; If an admin with access to the RADIUS token server runs a debug, they can see the user’s active directory password which they want to avoid.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question – Is it possible for ISE to separate the authentication request?&amp;nbsp; Something like this:&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;Supplicant sends credentials to ISE to authenticate against AD.&lt;/LI&gt;&lt;LI&gt;If AD credentials pass, supplicant sends the token to ISE to authenticate against RADIUS token server.&lt;/LI&gt;&lt;LI&gt;If pass, proceed to authorization policies.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or alternative:&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;Supplicant sends AD credentials and token to ISE for authentication.&lt;/LI&gt;&lt;LI&gt;ISE authenticates credentials against AD and sends the token only to the RADIUS token server.&lt;/LI&gt;&lt;LI&gt;If it passes, then proceed to authorization policies.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 26 Mar 2016 00:44:37 GMT</pubDate>
    <dc:creator>Phi Yim</dc:creator>
    <dc:date>2016-03-26T00:44:37Z</dc:date>
    <item>
      <title>ISE - External Identity Store - Two Factor Request Passes Token and Password</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443715#M539325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My customer is using ISE for TACACS and would like to enable two factor authentication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They currently have their two factor authentication server configured as an external identity store which works as expected.&amp;nbsp; Problem is, when ISE sends the request to the RADIUS token server for authentication, it sends the AD username/password along with the token.&amp;nbsp; If an admin with access to the RADIUS token server runs a debug, they can see the user’s active directory password which they want to avoid.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question – Is it possible for ISE to separate the authentication request?&amp;nbsp; Something like this:&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;Supplicant sends credentials to ISE to authenticate against AD.&lt;/LI&gt;&lt;LI&gt;If AD credentials pass, supplicant sends the token to ISE to authenticate against RADIUS token server.&lt;/LI&gt;&lt;LI&gt;If pass, proceed to authorization policies.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or alternative:&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;Supplicant sends AD credentials and token to ISE for authentication.&lt;/LI&gt;&lt;LI&gt;ISE authenticates credentials against AD and sends the token only to the RADIUS token server.&lt;/LI&gt;&lt;LI&gt;If it passes, then proceed to authorization policies.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Mar 2016 00:44:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443715#M539325</guid>
      <dc:creator>Phi Yim</dc:creator>
      <dc:date>2016-03-26T00:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - External Identity Store - Two Factor Request Passes Token and Password</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443716#M539327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Neither really supported by ISE today. I think your customer's token server supporting it because it has the inside knowledge which characters belong to OTP and the reset that of AD passwords.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What supported in ISE is CWA chaining -- to use AD to perform one auth (e.g. DOT1X) and then redirect to an ISE guest portal and authenticated by token.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Mar 2016 04:04:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443716#M539327</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-03-26T04:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - External Identity Store - Two Factor Request Passes Token and Password</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443717#M539328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also it is common to use different ID stores for login and enable, by using the TACACS dictionary.&lt;/P&gt;&lt;P&gt;Please see that is an option for your customers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Mar 2016 18:55:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443717#M539328</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-03-26T18:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - External Identity Store - Two Factor Request Passes Token and Password</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443718#M539330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for getting back to me.&amp;nbsp; If we use different ID stores for login and enable, the problem still exist if the customer chooses two factor for enable right?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2016 21:32:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443718#M539330</guid>
      <dc:creator>Phi Yim</dc:creator>
      <dc:date>2016-03-28T21:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - External Identity Store - Two Factor Request Passes Token and Password</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443719#M539332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yep, if customers choose it that way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMHO It's essential two factors with one ID store for login and another for enable so customers need not send AD credentials to OTP. Anyhow, it's up to the customers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2016 21:44:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-identity-store-two-factor-request-passes-token-and/m-p/3443719#M539332</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-03-28T21:44:16Z</dc:date>
    </item>
  </channel>
</rss>

