Cisco Cisco IP Contact Center Release 4.6.1 Release Note

Figure 103: Security Alert Dialog Box

2. If the encrypted flag is set:

–

The client starts with setting up an HTTPS connection.

–

If the client successfully connects to the server, the client sends the encrypted user
account and password.

After the HTTPS connection is established, the server sends the certificate to the
client.

After the HTTPS connection is established, the server sends the certificate to the
client. The client presents the certificate prompt (see the 

), unless it has been previously saved locally).

If the client cannot connect to the server, it prompts you to determine if it should
failover to try to connect to the server via HTTP, or not. If you select Yes, the client
sends in the user account and password in plain text once the HTTP connection is
established. However, it does not set the encrypted flag in the registry so that the
HTTPS connection will still be initiated the next time.

If you want to use the HTTP connection for all future connections, you must manully
unset the flag in the login screen.

During runtime, the initialization is the same for every HTTP request.

During upgrades on clients with Windows 2003, the secure connection is automatically
configured to the default setting of 443 for SSL.

During new installations on MS Windows 2000 and Windows 2003, the secure connection is
automatically configured to the default setting of 443 for SSL.

Note: ISE client is able to revert back to unencrypted communication over port 80 if it fails to
establish an HTTPS session.

ICM Scripting and Media Routing Guide Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)