<?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 Certificates are another way in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893351#M5884</link>
    <description>&lt;P&gt;Certificates are another way to provide the identity of a machine or user instead of a "password". The world of certificates and network authentication (dot1x) can be overwhelming, so I will try to explain the important concepts in this reply.&lt;BR /&gt;&lt;BR /&gt;There are two common authentication methods being used in today's wireless deployments:&lt;BR /&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; PEAPv0 which is based on username and password&lt;BR /&gt;&lt;STRONG&gt;2.&lt;/STRONG&gt; EAP-TLS which is based on a machine or user certificate but requires a PKI&lt;BR /&gt;&lt;BR /&gt;The process of getting the client connected and authenticated are similar for both methods:&lt;BR /&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; Client associates to the wireless network;&lt;BR /&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;. Client builds a protected tunnel with the authentication server. Based on the certificate used on the (RADIUS) &lt;STRONG&gt;server side&lt;/STRONG&gt; the client verifies that it is talking to the correct server so it knows that it is safe to continue;&lt;BR /&gt;&lt;STRONG&gt;3.&lt;/STRONG&gt; Client sends its credentials to the server (username/password with PEAPv0, certificate with EAP-TLS);&lt;BR /&gt;&lt;STRONG&gt;3a.&lt;/STRONG&gt; In case of EAP-TLS the certificate will be validated and read by the server. Usually the CN or SAN attribute found in the certificate will be used for the Active Directory lookup;&lt;BR /&gt;&lt;STRONG&gt;4. &lt;/STRONG&gt;Server validates the provided credentials by consulting Active Directory;&lt;BR /&gt;&lt;STRONG&gt;5. &lt;/STRONG&gt;Active Directory gives feedback and provided current status and all the memberships the related object has within Active Directory. This object can be a user account or computer in case of a machine certificate. &lt;BR /&gt;&lt;STRONG&gt;6. &lt;/STRONG&gt;Based on the policies within the authentication server certain information can be provided to the WLC (Examples are: deny, allow and a specified VLAN which should be used etc).&lt;BR /&gt;&lt;BR /&gt;If you want to deploy EAP-TLS the following things should be in place:&lt;BR /&gt;&lt;STRONG&gt;1. &lt;/STRONG&gt;A PKI&lt;STRONG&gt;, &lt;/STRONG&gt;preferable Microsoft's implementation which integrates within Active Directory&lt;STRONG&gt;;&lt;BR /&gt;2. &lt;/STRONG&gt;A authentication server for example Cisco ISE or Microsoft's NPS which uses a server certificate which can be actually verified by the clients &lt;EM&gt;(so signed by public CA or own PKI if all of the clients do have to CA cert of the PKI installed)&lt;/EM&gt;&lt;STRONG&gt;;&lt;BR /&gt;3.&lt;/STRONG&gt; Active Directory infrastructure with two GPOs deployed:&lt;BR /&gt;&lt;STRONG&gt;3a.&lt;/STRONG&gt; GPO to auto enroll certificates so clients will request a user/machine certificate;&lt;BR /&gt;&lt;STRONG&gt;3b. &lt;/STRONG&gt;GPO to configure the client with wireless settings;&lt;BR /&gt;&lt;STRONG&gt;4. &lt;/STRONG&gt;A RADIUS based connection between the WLC and the authentication server&lt;STRONG&gt;;&lt;BR /&gt;5. &lt;/STRONG&gt;Policies on the authentication server based on certain Active Directory groups so clients can be authenticated.&lt;BR /&gt;&lt;BR /&gt;Hopefully this helps to give some clarity, however if you have never have done any implementation I strongly advice to get some external help. Building a robust and secure PKI requires proper planning and a good design, so goes for the authentication services.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Please rate useful posts... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 12 Nov 2016 23:44:24 GMT</pubDate>
    <dc:creator>Freerk Terpstra</dc:creator>
    <dc:date>2016-11-12T23:44:24Z</dc:date>
    <item>
      <title>WLC and Client Certificate Authentication</title>
      <link>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893349#M5882</link>
      <description>&lt;P&gt;We are trying to implement certs for clients to use when connecting to the Enterprise Wireless Infrastructure with the WLC.&amp;nbsp; We use a MS Domain and use ACS.&amp;nbsp; What is the best way to implement this to a gain security posture and avoid evil twin issues, and ensure trusted clients are connected and authenticated.&amp;nbsp; Management wants to implement certificates for the clients connecting to the Wireless Controllers and AP's.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;There is a request to use real certificates and not self-signed certs, for PEAP Auth.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 12:01:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893349#M5882</guid>
      <dc:creator>Timothy Ventry</dc:creator>
      <dc:date>2021-07-05T12:01:16Z</dc:date>
    </item>
    <item>
      <title>Hi Tim did you find any</title>
      <link>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893350#M5883</link>
      <description>&lt;P&gt;Hi Tim did you find any documentation around this? I'm trying to do the same thing.&lt;/P&gt;
&lt;P&gt;user machine authenticate with a certificate onto wireless then then the user authenticates with AD.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2016 15:05:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893350#M5883</guid>
      <dc:creator>mickyq</dc:creator>
      <dc:date>2016-11-11T15:05:36Z</dc:date>
    </item>
    <item>
      <title>Certificates are another way</title>
      <link>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893351#M5884</link>
      <description>&lt;P&gt;Certificates are another way to provide the identity of a machine or user instead of a "password". The world of certificates and network authentication (dot1x) can be overwhelming, so I will try to explain the important concepts in this reply.&lt;BR /&gt;&lt;BR /&gt;There are two common authentication methods being used in today's wireless deployments:&lt;BR /&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; PEAPv0 which is based on username and password&lt;BR /&gt;&lt;STRONG&gt;2.&lt;/STRONG&gt; EAP-TLS which is based on a machine or user certificate but requires a PKI&lt;BR /&gt;&lt;BR /&gt;The process of getting the client connected and authenticated are similar for both methods:&lt;BR /&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; Client associates to the wireless network;&lt;BR /&gt;&lt;STRONG&gt;2&lt;/STRONG&gt;. Client builds a protected tunnel with the authentication server. Based on the certificate used on the (RADIUS) &lt;STRONG&gt;server side&lt;/STRONG&gt; the client verifies that it is talking to the correct server so it knows that it is safe to continue;&lt;BR /&gt;&lt;STRONG&gt;3.&lt;/STRONG&gt; Client sends its credentials to the server (username/password with PEAPv0, certificate with EAP-TLS);&lt;BR /&gt;&lt;STRONG&gt;3a.&lt;/STRONG&gt; In case of EAP-TLS the certificate will be validated and read by the server. Usually the CN or SAN attribute found in the certificate will be used for the Active Directory lookup;&lt;BR /&gt;&lt;STRONG&gt;4. &lt;/STRONG&gt;Server validates the provided credentials by consulting Active Directory;&lt;BR /&gt;&lt;STRONG&gt;5. &lt;/STRONG&gt;Active Directory gives feedback and provided current status and all the memberships the related object has within Active Directory. This object can be a user account or computer in case of a machine certificate. &lt;BR /&gt;&lt;STRONG&gt;6. &lt;/STRONG&gt;Based on the policies within the authentication server certain information can be provided to the WLC (Examples are: deny, allow and a specified VLAN which should be used etc).&lt;BR /&gt;&lt;BR /&gt;If you want to deploy EAP-TLS the following things should be in place:&lt;BR /&gt;&lt;STRONG&gt;1. &lt;/STRONG&gt;A PKI&lt;STRONG&gt;, &lt;/STRONG&gt;preferable Microsoft's implementation which integrates within Active Directory&lt;STRONG&gt;;&lt;BR /&gt;2. &lt;/STRONG&gt;A authentication server for example Cisco ISE or Microsoft's NPS which uses a server certificate which can be actually verified by the clients &lt;EM&gt;(so signed by public CA or own PKI if all of the clients do have to CA cert of the PKI installed)&lt;/EM&gt;&lt;STRONG&gt;;&lt;BR /&gt;3.&lt;/STRONG&gt; Active Directory infrastructure with two GPOs deployed:&lt;BR /&gt;&lt;STRONG&gt;3a.&lt;/STRONG&gt; GPO to auto enroll certificates so clients will request a user/machine certificate;&lt;BR /&gt;&lt;STRONG&gt;3b. &lt;/STRONG&gt;GPO to configure the client with wireless settings;&lt;BR /&gt;&lt;STRONG&gt;4. &lt;/STRONG&gt;A RADIUS based connection between the WLC and the authentication server&lt;STRONG&gt;;&lt;BR /&gt;5. &lt;/STRONG&gt;Policies on the authentication server based on certain Active Directory groups so clients can be authenticated.&lt;BR /&gt;&lt;BR /&gt;Hopefully this helps to give some clarity, however if you have never have done any implementation I strongly advice to get some external help. Building a robust and secure PKI requires proper planning and a good design, so goes for the authentication services.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Please rate useful posts... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Nov 2016 23:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/2893351#M5884</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2016-11-12T23:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Certificates are another way</title>
      <link>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/4820059#M254915</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Wanted your guidance on the below.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of my customer is trying to achieve Certificate based auth when the users are connecting on the wireless network. But he is trying to achieve that with having a NAC/RADIUS solution in place. But he does have a AD server in place. Is this achievable. And if yes then how is that. Do we require any additional component to add to the solution along with the AD server&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 07:33:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-and-client-certificate-authentication/m-p/4820059#M254915</guid>
      <dc:creator>Rahul Pawar</dc:creator>
      <dc:date>2023-04-24T07:33:49Z</dc:date>
    </item>
  </channel>
</rss>

