Avaya 3100 Mobile Communicator and Security Manual de usuario Pagina 87

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 116
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 86
Chapter 10: Server certificate management
This chapter describes the procedures that you use to manage server certificates. You implement a
certificate infrastructure to encrypt the following traffic:
• Signaling traffic exchanged between the client devices and the Avaya 3100 Mobile Communicator
Gateway. This type of traffic includes caller ID information, call setup commands, instant messaging,
and corporate directory search requests and results. BlackBerry clients do not require certificates if
deployed using the BlackBerry Enterprise Server (BES). The BES protects the data channel.
• Service management traffic exchanged between PC-based Web Administration Console clients and
the Avaya 3100 Mobile Communicator Gateway administration server. This type of traffic includes
log in requests and configuration updates.
Avaya 3100 Mobile Communicator supports
• Certificate Authority (CA) signed certificates—A certificate authority (CA) acts as a trusted third-
party that issues and validates the certificates. You can employ a commercial CA, such as VeriSign or
CACert, or build your own using tools such as those provided with Microsoft Exchange Server.
• Self-signed certificates—As an alternative to using a CA, you can generate your own certificates on
the Avaya 3100 Mobile Communicator Gateway. Avaya recommends that self-signed certificates be
used only for test purposes.
You implement the certificates on the Avaya 3100 Mobile Communicator Gateway server and Avaya
3100 Mobile Communicator Gateway Administration server.
The Avaya 3100 Mobile Communicator Gateway installation provides default, self-signed certificates, to
enable security immediately. However, self-signed certificates do not provide the same level of security
as CA-signed certificates. Self-signed certificates should be used only for test or demonstration purposes.
For information on generating self-signed certificates, see
Generating a self-signed certificate for Avaya
3100 Mobile Communicator Gateway Server on page 104.
Important:
On redundant systems, you must generate CSRs and obtain CA-signed certificates for both servers.
You must obtain the CA root certificate in two formats:
• PEM format for installation on the Avaya 3100 Mobile Communicator Gateway Administration Server,
client PCs, and Windows Mobile 6 devices.
• DER format for installation on the Avaya 3100 Mobile Communicator Gateway server, Windows
Mobile 5 devices, Nokia devices, and RIM BlackBerry devices.
To obtain the CA root or intermediate certificate, use the certificate management tool provided by the CA.
Administration and Security October 2010 87
Vista de pagina 86
1 2 ... 82 83 84 85 86 87 88 89 90 91 92 ... 115 116

Comentarios a estos manuales

Sin comentarios