<?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 Yes, it is possible to build a similar process for wired... in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/authentication-method-for-wired-and-wireless/m-p/4845530#M1101040</link>
    <description>Yes, it is possible to build a similar process for wired and wireless networks using a combination of 802.1X authentication, EAP-TLS for certificate-based authentication, and RADIUS for password-based authentication and authorization. Here's a high-level overview of the process:&lt;BR /&gt;&lt;BR /&gt;1. Configure your wired and wireless infrastructure to support 802.1X authentication. This typically involves configuring your switches and wireless access points to act as Authenticators for 802.1X.&lt;BR /&gt;&lt;BR /&gt;2. Set up a RADIUS server, such as Cisco Identity Services Engine (ISE), if you haven't already. This server will handle the password-based authentication and authorization.&lt;BR /&gt;&lt;BR /&gt;3. Configure your RADIUS server to use EAP-TLS as the authentication method. EAP-TLS supports mutual authentication using client and server certificates. You will need to import the Certificate Authority (CA) certificate that issued the client and server certificates to the RADIUS server.&lt;BR /&gt;&lt;BR /&gt;4. Configure your network clients to use 802.1X and EAP-TLS for authentication. This typically involves installing a client certificate on each client device and configuring the network settings to use 802.1X with EAP-TLS.&lt;BR /&gt;&lt;BR /&gt;5. If you want to extract the username from the client certificate's Common Name (CN) and use it for password-based authentication, you will need to configure your RADIUS server to do so. In Cisco ISE, this can be done by creating a custom EAP-TLS authentication rule that extracts the username from the CN and passes it to the RADIUS server for password-based authentication.&lt;BR /&gt;&lt;BR /&gt;6. Configure your RADIUS server to perform password-based authentication and authorization once the client certificate has been verified.&lt;BR /&gt;&lt;BR /&gt;7. Test your wired and wireless network to ensure that the authentication process works as expected. Clients should be authenticated first using their certificates and then using their passwords.&lt;BR /&gt;&lt;BR /&gt;By following these steps, you should be able to create a secure wired and wireless network that uses both client certificate and password-based authentication.</description>
    <pubDate>Tue, 30 May 2023 15:52:22 GMT</pubDate>
    <dc:creator>Cisco_Virtual_Engineer</dc:creator>
    <dc:date>2023-05-30T15:52:22Z</dc:date>
    <item>
      <title>authentication method for wired and wireless</title>
      <link>https://community.cisco.com/t5/network-security/authentication-method-for-wired-and-wireless/m-p/4843723#M1100916</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm a starter in configure an enterprise level auth for wired and wireless.&lt;/P&gt;&lt;P&gt;I previously config a VPN use cisco FTD and anyconnect as client. the authentication on VPN I can use both certificate and password, I notice that RADIUS server in this case only do the password authentication and authorization, FTD server will take after the client certificate check before the password check.&lt;/P&gt;&lt;P&gt;Is it possible to build a semiller proccess for wired and wireless? both client certificate and password auth&lt;/P&gt;&lt;P&gt;First verify server and client certificate, then check password (get username from client certificate comman name)&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 16:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authentication-method-for-wired-and-wireless/m-p/4843723#M1100916</guid>
      <dc:creator>chengl031</dc:creator>
      <dc:date>2023-05-26T16:24:44Z</dc:date>
    </item>
    <item>
      <title>Yes, it is possible to build a similar process for wired...</title>
      <link>https://community.cisco.com/t5/network-security/authentication-method-for-wired-and-wireless/m-p/4845530#M1101040</link>
      <description>Yes, it is possible to build a similar process for wired and wireless networks using a combination of 802.1X authentication, EAP-TLS for certificate-based authentication, and RADIUS for password-based authentication and authorization. Here's a high-level overview of the process:&lt;BR /&gt;&lt;BR /&gt;1. Configure your wired and wireless infrastructure to support 802.1X authentication. This typically involves configuring your switches and wireless access points to act as Authenticators for 802.1X.&lt;BR /&gt;&lt;BR /&gt;2. Set up a RADIUS server, such as Cisco Identity Services Engine (ISE), if you haven't already. This server will handle the password-based authentication and authorization.&lt;BR /&gt;&lt;BR /&gt;3. Configure your RADIUS server to use EAP-TLS as the authentication method. EAP-TLS supports mutual authentication using client and server certificates. You will need to import the Certificate Authority (CA) certificate that issued the client and server certificates to the RADIUS server.&lt;BR /&gt;&lt;BR /&gt;4. Configure your network clients to use 802.1X and EAP-TLS for authentication. This typically involves installing a client certificate on each client device and configuring the network settings to use 802.1X with EAP-TLS.&lt;BR /&gt;&lt;BR /&gt;5. If you want to extract the username from the client certificate's Common Name (CN) and use it for password-based authentication, you will need to configure your RADIUS server to do so. In Cisco ISE, this can be done by creating a custom EAP-TLS authentication rule that extracts the username from the CN and passes it to the RADIUS server for password-based authentication.&lt;BR /&gt;&lt;BR /&gt;6. Configure your RADIUS server to perform password-based authentication and authorization once the client certificate has been verified.&lt;BR /&gt;&lt;BR /&gt;7. Test your wired and wireless network to ensure that the authentication process works as expected. Clients should be authenticated first using their certificates and then using their passwords.&lt;BR /&gt;&lt;BR /&gt;By following these steps, you should be able to create a secure wired and wireless network that uses both client certificate and password-based authentication.</description>
      <pubDate>Tue, 30 May 2023 15:52:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/authentication-method-for-wired-and-wireless/m-p/4845530#M1101040</guid>
      <dc:creator>Cisco_Virtual_Engineer</dc:creator>
      <dc:date>2023-05-30T15:52:22Z</dc:date>
    </item>
  </channel>
</rss>

