<?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: User authentication during Remote Desktop session in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3891456#M471471</link>
    <description>&lt;P&gt;You may also try chaining DOT1X machine auth with Easy Connect.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jul 2019 00:18:57 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2019-07-17T00:18:57Z</dc:date>
    <item>
      <title>User authentication during Remote Desktop session</title>
      <link>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3890757#M471462</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With Windows native 802.1x supplicant and "User or Machine authentication" enabled, only machine authentication started when a user establish a remote desktop session to an existing connected endpoint. Beside using AnyConnect NAM, do we have any option to authorize an endpoint based on user identity. In our current setup, machine authentication will receive a different set of authorization policy. Our objective is to maintain authorization policy based on previously logged on user identity.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Wing Churn&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2019 04:20:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3890757#M471462</guid>
      <dc:creator>wileong</dc:creator>
      <dc:date>2019-07-16T04:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: User authentication during Remote Desktop session</title>
      <link>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3891383#M471466</link>
      <description>Pretty sure there isn't a way. I will check with another expert.</description>
      <pubDate>Tue, 16 Jul 2019 21:27:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3891383#M471466</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-07-16T21:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: User authentication during Remote Desktop session</title>
      <link>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3891456#M471471</link>
      <description>&lt;P&gt;You may also try chaining DOT1X machine auth with Easy Connect.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 00:18:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3891456#M471471</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-07-17T00:18:57Z</dc:date>
    </item>
    <item>
      <title>Re: User authentication during Remote Desktop session</title>
      <link>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3893196#M471477</link>
      <description>&lt;P&gt;Hi Hsing,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would you mind sharing any document around chaining 802.1x with Easy Connect?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Wing Churn&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 02:28:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/user-authentication-during-remote-desktop-session/m-p/3893196#M471477</guid>
      <dc:creator>wileong</dc:creator>
      <dc:date>2019-07-19T02:28:44Z</dc:date>
    </item>
  </channel>
</rss>

