Configuring 802.1x Network Device Authentication¶
|Enable 802.1x security|
|Authentication||TLS (this is the only available setting)|
|Enable 802.1X Support for Legacy Switches|
This section describes the components you need to configure 802.1x authentication, and the detailed steps you need to follow to configure the authentication. The instructions provided in this topic were done on a Microsoft 2019 Datacenter. If you are performing these instructions from a different version of Microsoft Server you may have to consult your server documentation for any changes in procedures.
Preparing for 802.1x Configuration¶
The supported 802.1x configuration has the PCoIP Zero Client pre-populated with a proper certificate. It then connects and presents the certificate to the 802.1x switch and is authenticated. PCoIP Zero Clients will also connect under a different configuration of the switch which has the MAC address of authorized endpoints stored in it's configuration.
Using certificates to sign other certificates
If a certificate is used to sign another certificate, it must have the digitalSignature key usage field enabled.
Before you begin the configuration process, make sure you have these components:
- Tera2 PCoIP Zero Client with firmware 5.x or newer
- PCoIP Management Console 2 or newer
- Windows Server 2019 with AD DS (Active Directory Domain Services)
- Windows Server 2019 with AD CS (Active Directory Certificate Services)
- Windows Server 2019 with NPS (Network Policy and Access Services)
- A switch with 802.1x support configured
Configuring Devices for 802.1x Authentication¶
To configure 802.1x device authentication, complete the following steps:
- Create a 802.1x Client User.
- Export the Root CA Certificate.
- Create a Certificate Template for 802.1x Client Authentication.
- Issue the 802.1x Client Certificate.
- Export the 802.1x Client Certificate.
- Convert the Certificate Format from .pfx to .pem.
- Import the 802.1x Client Certificate into the Client User Account.
- Import the Certificates to the 802.1x Client Device.
The following sections assume you are using Windows Server 2019 Datacenter
The instructions in the following sections are based on Windows Server 2019 Datacenter. If you are using a newer version of Windows Server, the steps may vary slightly.
Create a 802.1x Client User¶
In the Windows server, create a 802.1x client user.
Create a 802.1x Client User
- Log in to the Windows server.
- Click Start > Windows Administrative Tools > Active Directory Users and Computers.
- Navigate to Roles > Active Directory Domain Services > Active Directory Users and Computers > <your_domain.local> > Users.
- Right-click Users, select New > User, and follow the wizard.
(Example: Create a user called pcoip_endpoint which would have a UPN name of pcoip_endpoint@<mydomain.local>)
Export the Root CA Certificate¶
In the Certificate Authority (CA) server, export the root CA certificate.
To export the root CA certificate:
- Log in to the Certificate Authority (CA) server.
- Open a Microsoft Management Console window (for example,enter mmc.exe in the Start menu search field).
- From the console window, select File > Add/Remove Snap-in.
- Add the Certificates snap-in, selecting Computer account and then Local computer.
- Click OK to close the Add or Remove Snap-ins dialog.
- From the console, select Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
- In the right panel, right-click the certificate, and select All Tasks > Export.
- Follow the wizard to export the certificate:
- Select Base-64 encoded X.509 (.CER) and click Next.
- Click Browse, specify a name and location for the certificate, and then click Save.
- Click Finish, and then click OK.
Create a Certificate Template for 802.1x Client Authentication¶
In the CA Server, create a certificate template for client authentication.
To create a certificate template for client authentication:
- From the CA Server, click Start > Administrative Tools > Certification Authority.
- Expand the tree for your CA.
- Right-click Certificate Templates, and then click Manage.
- Right-click the Computer template, and then click Duplicate Template.
Configure the template as follows:
From the Compatibility tab, select Windows Server 2003.
From the Extensions tab, ensure the Digital signature is included in the certificate Key Usage
From the General tab, enter a name for the template (for example, PCoIP Endpoint 802.1x) and change the validity period to match the organization’s security policy.
From the Request Handling tab, select Allow private key to be exported.
From the Subject Name tab, select Supply in the request and then click OK.
From the Security tab, select the user who will be requesting the certificate, and give Enroll permission to this user.
Click OK and close the Certificate Templates Console window.
From the Certification Authority window, right-click Certificate Templates, select New, and then click Certificate Template to Issue.
Select the certificate you just created (that is, PCoIP Endpoint 802.1x), and then click OK. The template will now appear in the Certificate Templates list.
Close the window.
Issue the 802.1x Client Certificate¶
From the CA Web Enrollment interface for the certificate server, issue the client certificate.
To issue the 802.1x client certificate:
Use Internet Explorer to log in to certificate server
Do not use any other browser except Internet Explorer to log into the certificate server or some options may not appear.
Using Internet Explorer on your local machine, go to your Certificate Authority URL using the format https://<server&tgt/certsrv/ (for example, https://ca.domain.local/certsrv/).
Click Request a certificate and then click advanced certificate request.
Click Create and submit a request to this CA.
From the pop-up window, click Yes.
Fill out the Advanced Certificate Request form as follows:
In the Certificate Template section, select the certificate for clients (for example, PCoIP Endpoint 802.1x).
In the Identifying Information for Offline Template section, enter the account name in the Name field. The other fields are not required.
The other fields are not required.
Enter the same name as the universal principal name of the client user
The name you enter in the Name field must be the universal principal name (UPN) of the client user you created in Create a 802.1x Client User(for example, pcoip_endpoint@mydomainlocal)
In the Key Options section, check Mark keys as exportable.
In the Additional Options section, set the Request Format to PKCS10.
If desired, enter a name in the Friendly Name field.
From the Certificate Issued window, click the Install this certificate link.
(This will save the certificate in the Current User > Personal store.)
Export the 802.1x Client Certificate¶
From the machine on which you issued the certificate, export the client certificate.
To export the client certificate:
From the machine on which you issued the certificate, open a Microsoft Management Console window (for example, enter
mmc.exein the Start menu search field).
From the console window, select File > Add/Remove Snap-in.
Add the Certificates snap-in, selecting My user account.
Click Finish, and then click OK to close the Add or Remove Snap-ins dialog.
Select Certificates - Current User > Personal > Certificates.
In the right panel, right-click the certificate, and select All Tasks > Export.
Follow the Certificate Export wizard to export the certificate by clicking Next:
Click Yes, export the private key.
Select Personal Information Exchange - PKCS #12 (.PFX).
Enter a password for the certificate.
Click Browse, specify a name and location for the certificate, and then click Save.
Click Next, Finish, and then click OK.
Repeat Steps 5 to 7 again to export the PCoIP endpoint certificate, but this time without the private key (No, do not export the private key), selecting the DER encoded binary X.509 (.CER) format instead of the PKCS format.
.cerfile to a location where it can be accessed by the Domain Controller and imported into Active Directory.
Convert the Certificate Format from .pfx to .pem¶
Using OpenSSL, convert the certificate format from .pfx to .pem.
To convert the certificate format from .pfx to .pem:
Download and install Windows OpenSSL from https://www.slproweb.com/products/Win32OpenSSL.html. (The light version is sufficient.)
Copy the .pfx client certificate file you saved above to the C:\OpenSSL-Win32\bin directory.
Open a command prompt window (C:\OpenSSL-Win32\bin), and enter the following command to convert the certificate format from .pfx to .pem where <client_cert> is the name of the .pfx certificate file you saved to your local machine.
openssl.exe pkcs12 ‑in <client_cert>.pfx ‑out <client_cert>.pem ‑nodes
When prompted, enter the password for the certificate file.
At the command prompt, enter the following command to create an RSA private key file where
is the name of the .pem certificate file you created in the previous step.
openssl.exe rsa –in <client_cert>.pem –out < client_cert>_rsa.pem
Open both the original .pem file and the RSA .pem file you just created. The RSA .pem file contains only an RSA private key. Because the PCoIP Endpoint certificate requires its private key in RSA format, you need to replace its private key with this RSA private key.
Copy the entire contents of the RSA .pem file (everything from
-----BEGIN RSA PRIVATE KEY -----to
-----END RSA PRIVATE KEY-----), and paste it into the original .pem file, replacing its private key with this RSA private key.
RSA .pem file
In other words, make sure that all the text from
-----BEGIN PRIVATE KEY-----to
-----END PRIVATE KEY(including the dashes) in the original .pem file is replaced with the contents of
-----BEGIN RSA PRIVATE KEY -----to
-----END RSA PRIVATE KEY-----(including the dashes) from the RSA .pem file.
Save the original .pem file and close it. The certificate is now ready to be uploaded to the PCoIP Endpoint.
Import the 802.1x Client Certificate into the Client User Account¶
In the Windows Domain Controller, import the client certificate into the client user account.
To import the 802.1x client certificate into the client user account:
Log in to the Windows Domain Controller.
Click Start > Administrative Tools > Active Directory Users and Computers.
From the View menu, select Advanced Features.
Navigate to the user you created for the PCoIP Endpoint.
Right-click the user, and select Name Mappings.
In the X.509 Certificates section, click Add.
Locate and select the PCoIP Endpoint certificate you exported that does not contain the private key (This file was saved to a network location in step 9 of Export the 802.1x Client Certificate.)
Make sure both identity boxes are selected and click OK, and then click OK again.
Import the Certificates to the 802.1x Client Device¶
From the PCoIP endpoint’s AWI, import the certificates.
To import the certificates into a profile using the PCoIP Management Console, see the PCoIP® Management Console Administrators’ Guide.
To import the certificates to a device using the AWI:
From a browser, log into the AWI for the PCoIP Endpoint.
From the AWI, select Upload > Certificate.
Upload both the Root CA certificate and the certificate with the private key, using the Browse button to locate each certificate and the Upload button to upload them.
From the OSD or AWI, select Configuration > Network.
Select Enable 802.1x Security.
Click Choose beside the Client Certificate field.
Select the certificate with the private key, and then click Select.
Enter the identity name of the certificate. Typically, this is the universal principal name (UPN) that appears after Subject: (for example, email@example.com).
Windows server may be configured to use the certificate’s Subject, the Subject Alternative Name, or another field
For the identity name, your Windows server may be configured to use the certificate’s Subject, the Subject Alternative Name, or another field. Check with your administrator.
To enable greater 802.1x compatibility for older switches on the network, select Enable 802.1X Support for Legacy Switches. This setting is only available from the PCoIP endpoints AWI Network page.
Click Apply, and then click Reset.
Getting more information about 802.1x
For more information about 802.1x, see the following Knowledge Base articles, available from the Teradici Support Center: