Home » HP Manuals » Desktops » HP t310 » Manual Viewer

HP t310 PCoIP Administrator's Guide - Page 131

Uploading Certificates for 802.1X Authentication, Certificate Upload, Network

Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

PCoIP Administrator's Guide 8.3.1 Uploading Certificates for 802.1X Authentication The following are some general guidelines when using 802.1X authentication. For detailed information, see Knowledge Base support topic 15134-1063 on the Teradici support site. l 802.1X authentication requires two certificates-an 802.1X client certificate and an 802.1X server CA root certificate. l The 802.1X client certificate must be in .pem format and contain a private key that uses RSA encryption. If the certificate is in a different format, you must first convert the certificate, including the private key, to .pem format before uploading it. l After uploading the 802.1X client certificate from the Certificate Upload page, you must configure 802.1X authentication from the Network page. This entails enabling 802.1X authentication, entering an identity string for the zero device, selecting the correct 802.1X client certificate from the drop-down list, and then applying your settings. For more information, see section 4.2. l The 802.1X server CA root certificate must be in .pem format, but should not need to contain a private key. If the certificate is in a different format, you must convert it to .pem format before uploading it. This certificate does not require configuration from the Network page. l Both the 802.1X client certificate and the 802.1X server CA root certificate must be less than 6 KB; otherwise, you will not be able to upload them. Some certificate files may contain multiple certificates. If your certificate file is too large and it has multiple certificates within, you can open the file in a text editor, then copy and save each certificate to its own file. TER0606004 Issue 16 131

Section	Page
Revision History	3
Table of Figures	12
Table of Tables	16
Definitions	18
1 Introduction	20
1.1 About this Document	20
1.2 Menu and Page Overview	21
2 Administrative Web Interface Overview	25
2.1 About the Page Layout	25
2.2 Supported Web Browsers	26
2.3 Administrative Web Interface IP Address	27
2.4 Administrative Interface Security	27
2.4.1 Installing the CA Root Certificate	27
2.5 Logging In	27
2.6 Viewing the Home Page	28
2.7 About the Administrative Interface Menus	32
2.7.1 Viewing the Configuration Menu	33
2.7.2 Viewing the Permissions Menu	34
2.7.3 Viewing the Diagnostics Menu	34
2.7.4 Viewing the Information Menu	34
2.7.5 Viewing the Upload Menu	34
3 Working with the On Screen Display (OSD)	35
3.1 About the Connect Window	35
3.1.1 Connect Button	36
3.2 About the OSD Options Menu	36
4 Configuring the Device	37
4.1 Initial Setup Page	37
4.2 Configuring the Network Settings	41
4.3 Configuring the IPv6 Settings for a Device	44
4.4 Adding Custom Information for the Device	47
4.5 Configuring the Discovery Mechanism	49
4.6 Configuring the SNMP Agent	51
4.7 Configuring the Session	51
4.7.1 Configuring a Direct Session	53
4.7.2 Configuring a Direct Session with SLP Host Discovery	58
4.7.3 Configuring a VMware View Connection	62
4.7.4 Configuring Kiosk Mode	70
4.7.5 Configuring a View Connection Server + Imprivata OneSign Connection	76
4.7.6 Enabling or Disabling Connection Management	80
4.8 Controlling the Bandwidth for PCoIP Sessions	85
4.9 Setting the User Interface Language	86
4.10 Configuring the OSD Screen-saver Timeout	88
4.11 Adjusting the Image Quality	89
4.12 Enabling the Host Driver Function	94
4.13 Configuring the NTP Parameters	95
4.14 Updating the Password for a Device	96
4.15 Resetting the Parameters to Factory Default Values	97
4.16 Configuring the EDID Override Mode	99
4.17 Enabling Monitor Emulation	101
4.18 Enabling or Disabling the OSD Configuration Menus	102
4.19 Enabling or Disabling the Web Server	102
5 Setting up the User Permissions	104
5.1 Specifying USB Devices	104
5.2 Configuring the Audio Parameters	106
5.3 Setting up the Client's Power-off Permissions	107
6 Using the Diagnostic Tools	109
6.1 Viewing and Clearing Event Log Messages	109
6.1.1 Syslog Features	109
6.2 Controlling the Device Session	112
6.3 Viewing PCoIP Protocol Statistics	113
6.4 Working with the Host Information and Power State	117
6.5 Generating an Audio Test Tone from the Client	118
6.6 Viewing a Test Pattern on the Client's Display	119
6.7 Resetting the Device Processor	120
6.8 Determining if a Device is Reachable	121
7 Viewing Device Information	123
7.1 Viewing the Version Information	123
7.2 Viewing the Attached Devices	125
8 Uploading to the Device	128
8.1 Uploading Firmware to the Device	128
8.1.1 Firmware Upload Process Example:	128
8.2 Uploading a Logo to the Device	129
8.2.1 OSD Logo Upload Process Example	130
8.3 Uploading the Certificate	130
8.3.1 Uploading Certificates for 802.1X Authentication	131
9 Configuring the User Settings	132
9.1 Configuring VMware View Certificate Checking	132
9.2 Configuring the Mouse Settings	133
9.3 Changing the Keyboard Repeat Settings	134
9.4 Adjusting the Image Quality from the OSD	135
9.5 Configuring the Display Topology	135
9.6 Configuring the Touch Screen	138
9.6.1 Installing the Touch Screen to the Zero Client	139
9.6.2 Setting up the Touch Screen as a Bridged Device	139
9.6.3 Configuring the Zero Client to Automatically Log into a VMware View Host	140
10 About the Overlay Windows	142
10.1 Network Connection Lost Overlay	142
10.2 Preparing Desktop Overlay	142
10.3 USB Device Not Authorized Overlay	143
10.4 USB Over Current Notice Overlay	143
10.5 USB Device Not Supported Behind a High-speed Hub Overlay	143
10.6 Resolution Not Supported Overlay	143
10.7 Half Duplex Overlay	144
10.8 Video Source Overlays	144
11 Using Smart Cards with PCoIP Zero Clients	146
11.1 Smart Card Requirements	146
11.1.1 Virtual Desktop Environment	146
11.1.2 Supported USB Card Readers	146
11.1.3 CAC Smart Card Properties	147
11.1.4 .Net Smart Card Properties	147
11.1.5 Communication Protocol	147
11.1.6 Card Certificate Requirements	147
11.1.7 Tested Smart Card Models	147
11.2 Using a Smart Card to Connect to a VMware View Brokered Session	148
Appendix A: Usage Examples Overview	151
A.1 Peer-to-Peer Direct Connection Example	151
A.1.1 Configuring the Client Peer-to-Peer Operation	151
A.1.2 Configuring the Host Peer-to-Peer Operation	152
A.1.3 Initiating the Peer-to-Peer Session	153
A.2 DHCP and Enable Host Discovery Example	154
A.2.1 Configuring the Client for DHCP and SLP Discovery	154
A.2.2 Configuring the Host for Host DHCP and SLP Discovery	156
A.2.3 Initiating an SLP Discovery Session	158
A.3 USB Permissions Example	158
A.3.1 Authorizing USB Device By Class	158
A.3.2 Authorizing USB Device By Vendor/Product ID	159
Appendix B: Client Language and Keyboard Support	161
B.1 Languages Supported by the Client	161

Match case Limit results 1 per page

8.3.1

Uploading Certificates for 802.1X Authentication

The following are some general guidelines when using 802.1X authentication. For detailed

information, see Knowledge Base support topic 15134-1063 on the

Teradici

support

site

802.1X authentication requires two certificates—an 802.1X client certificate and an

802.1X server CA root certificate.

The 802.1X client certificate must be in .pem format and contain a private key that uses

RSA encryption. If the certificate is in a different format, you must first convert the

certificate, including the private key, to .pem format before uploading it.

After uploading the 802.1X client certificate from the

Certificate Upload

page, you

must configure 802.1X authentication from the

Network

page. This entails enabling

802.1X authentication, entering an identity string for the zero device, selecting the

correct 802.1X client certificate from the drop-down list, and then applying your settings.

For more information, see section

4.2

The 802.1X server CA root certificate must be in .pem format, but should not need to

contain a private key. If the certificate is in a different format, you must convert it to

.pem format before uploading it. This certificate does not require configuration from the

Network

page.

Both the 802.1X client certificate and the 802.1X server CA root certificate must be less

than 6 KB; otherwise, you will not be able to upload them. Some certificate files may

contain multiple certificates. If your certificate file is too large and it has multiple

certificates within, you can open the file in a text editor, then copy and save each

certificate to its own file.

TER0606004 Issue 16

131

PCoIP Administrator's Guide