<?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 Client Authentication using MAC and AD account in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517292#M306709</link>
    <description>&lt;P&gt;I want to control user devices through their MAC address and AD account when accessing the wireless network. That means, to access the wireless network, the device must have its MAC address registered beforehand and log in with the correct AD account. How can I implement this on a Meraki MR device?&lt;/P&gt;</description>
    <pubDate>Sun, 21 Jul 2024 09:30:17 GMT</pubDate>
    <dc:creator>ajiang1</dc:creator>
    <dc:date>2024-07-21T09:30:17Z</dc:date>
    <item>
      <title>Client Authentication using MAC and AD account</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517292#M306709</link>
      <description>&lt;P&gt;I want to control user devices through their MAC address and AD account when accessing the wireless network. That means, to access the wireless network, the device must have its MAC address registered beforehand and log in with the correct AD account. How can I implement this on a Meraki MR device?&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jul 2024 09:30:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517292#M306709</guid>
      <dc:creator>ajiang1</dc:creator>
      <dc:date>2024-07-21T09:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: Client Authentication using MAC and AD account</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517293#M306710</link>
      <description>&lt;P&gt;This is really a function of the Radius server that you are using.  If the radius server is able to take into account both factors (MAC + AD account) when deciding to provide or deny access then yes.&lt;/P&gt;&lt;P&gt;Windows built-in radius server (NPS) is not able to do that.  This can be performed with more advanced radius servers, such as Cisco ISE or others.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If what you are trying to achieve is that employees login onto wireless (AD auth) only with their corporate issued PCs then I would suggest to use Machine Authentication rather than username/password.  With Machine Authentication the Radius server verifies with AD if that machine belongs to the domain.  Then the user will be validated when they login into the machine.  Assuming that this is a Windows environment.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jul 2024 09:40:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517293#M306710</guid>
      <dc:creator>ppurroy</dc:creator>
      <dc:date>2024-07-21T09:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: Client Authentication using MAC and AD account</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517294#M306711</link>
      <description>&lt;P&gt;Thank you, Purroy.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jul 2024 15:12:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517294#M306711</guid>
      <dc:creator>ajiang1</dc:creator>
      <dc:date>2024-07-21T15:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Client Authentication using MAC and AD account</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517295#M306712</link>
      <description>&lt;P&gt;Because Meraki group policies are applied based on Mac address, you could set the default Wireless Firewall rule to deny everything, and then create a group policy called something like "Approved", which overrides the firewall rule and allows access, and apply it to every machine that is approved to access the network.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jul 2024 21:05:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517295#M306712</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2024-07-21T21:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: Client Authentication using MAC and AD account</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517296#M306713</link>
      <description>&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2025 17:19:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-using-mac-and-ad-account/m-p/5517296#M306713</guid>
      <dc:creator>Evgeniy Volokhovich</dc:creator>
      <dc:date>2025-02-28T17:19:33Z</dc:date>
    </item>
  </channel>
</rss>

