Wavelink Avalanche Site Edition Java Console User Guide

More documents

Recommendations

Info

Appendix A: SSL Certificates 182 Appendix A: SSL Certificates The Avalanche Web Console uses Hypertext Transfer Protocol (http) by default, which is not encrypted. If you want your information to be encrypted, you can configure Avalanche to use https with an SSL certificate instead. If you intend to use Avalanche with an SSL certificate for a secure connection, you have the options of purchasing a certificate through a third‐party Certificate Authority (such as Verisign), or creating a self‐signed certificate. NOTE If you create a self‐signed certificate, web browsers will not initially recognize the certificate and will display warning messages that the site is not trusted. They may require you to make an exception in order to connect to the enterprise server. The connection will be encrypted, however. This section contains instructions for the following tasks: • Implementing a Certificate from a Certificate Authority • Implementing a Self‐Signed Certificate Implementing a Certificate from a Certificate Authority You can choose to use Avalanche with a certificate from a Certificate Authority. Note that the following instructions are based upon acquiring a certificate through the certificate authority, Verisign. The steps may vary somewhat when using another certificate authority vendor. Wavelink strongly recommends that you backup the keystore file, the actual certificate file, the intermediate certificate, the certificate request, and the server.xml document after you have implemented your certificate. This would include the following files: • amckeystore.keystore • [your certificate].cer • intermediateCA.cer • certreq.csr
Appendix A: SSL Certificates 183 • server.xml This section contains the following tasks for obtaining an SSL certificate from a certificate authority: • Creating a Keystore • Generating the Certificate Signing Request • Importing an Intermediate Certificate • Importing a Certificate • Activating SSL for Tomcat • Accessing the Web Console over a Secure Connection • Troubleshooting Creating a Keystore To create a keystore for the certificate, use the keytool.exe utility. You will need to provide a Common Name (domain name), organizational unit, organization, city, state, and country code. You will also need to provide a keystore name and passwords for the keystore and alias. These are arbitrary, but should be noted for future reference. To generate a keystore for the certificate: 1 From a command line, navigate to: [Avalanche installation directory]\JRE\Bin 2 Use the command: keytool -genkey -alias amccert -keyalg RSA -keystore amckeystore.keystore 3 At the prompt Enter keystore password, type the keystore password. When prompted, re‐enter the password. 4 At the prompt What is your first and last name, type the Common Name.
Page 1 and 2:
Wavelink Avalanche Site Edition Jav
Page 3 and 4:
Table of Contents 1 Table of Conten
Page 5 and 6:
Table of Contents 3 Configuring Sch
Page 7 and 8:
Table of Contents 5 Mobile Device P
Page 9 and 10:
Chapter 1: Introduction 7 Chapter 1
Page 11 and 12:
Chapter 1: Introduction 9 • Locat
Page 13 and 14:
Chapter 1: Introduction 11 Once you
Page 15 and 16:
Chapter 2: Installing Avalanche 13
Page 17 and 18:
Chapter 3: Licensing 15 variety of
Page 19 and 20:
Chapter 3: Licensing 17 Figure 3-1.
Page 21 and 22:
Chapter 3: Licensing 19 To import a
Page 23 and 24:
Chapter 3: Licensing 21 NOTE If you
Page 25 and 26:
Chapter 4: Avalanche Console 23 Cha
Page 27 and 28:
Chapter 4: Avalanche Console 25 •
Page 29 and 30:
Chapter 4: Avalanche Console 27 Pro
Page 31 and 32:
Chapter 4: Avalanche Console 29 Whi
Page 33 and 34:
Chapter 4: Avalanche Console 31 3 I
Page 35 and 36:
Chapter 4: Avalanche Console 33 Sch
Page 37 and 38:
Chapter 4: Avalanche Console 35 Con
Page 39 and 40:
Chapter 4: Avalanche Console 37 Par
Page 41 and 42:
Chapter 4: Avalanche Console 39 Fro
Page 43 and 44:
Chapter 4: Avalanche Console 41 NOT
Page 45 and 46:
Chapter 5: Managing User Accounts 4
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Chapter 6: Managing Sites and Locat
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Chapter 7: Managing Network Profile
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Chapter 8: Managing Scan to Configu
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Chapter 9: Managing the Mobile Devi
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Chapter 10: Managing Software Profi
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Chapter 11: Managing Mobile Devices
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134: Chapter 11: Managing Mobile Devices
Page 149 and 150: Chapter 12: Managing Mobile Device
Page 155 and 156: Chapter 13: Managing Alert Profiles
Page 165 and 166: Chapter 14: Using Selection Criteri
Page 181 and 182: Chapter 15: Using the Task Schedule
Page 183: Chapter 15: Using the Task Schedule
Page 187 and 188: Appendix A: SSL Certificates 185 Ge
Page 189 and 190: Appendix A: SSL Certificates 187 3
Page 191 and 192: Appendix A: SSL Certificates 189 to
Page 193 and 194: Appendix A: SSL Certificates 191 ke
Page 195 and 196: Appendix B: Avalanche Services 193
Page 197 and 198: Appendix C: Port Information 195 Mo
Page 199 and 200: Glossary 197 Glossary ActiveSync Ad
Page 201 and 202: Glossary 199 ESSID Exclusion Window
Page 203 and 204: Glossary 201 Remote Control Scan to
Page 205 and 206: Index 203 Index A activating Avalan
Page 207 and 208: Index 205 scheduled settings 66 WLA
show all

Wavelink Avalanche Site Edition Java Console User Guide

Create successful ePaper yourself

Delete template?

Save as template?