Register Expressway-C connector hosts to Cloud
Hybrid Services use software connectors hosted on Expressway-C to securely connect Webex to your organization's environment. Use this procedure to register Expressway-C resources to the cloud.
After you complete the registration steps, the connector software is automatically deployed on your on-premises Expressway-C.
Before you begin
-
Make sure your Expressway-C is running on a version that's supported for hybrid services. See the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation (https://help.webex.com/article/ruyceab) for more information about which versions are supported for new and existing registrations to the cloud.
-
Sign out of any open connections to the Expressway-C interface that are open in other browser tabs.
-
If your on-premises environment proxies the outbound traffic, you must first enter the details of the proxy server on
before you complete this procedure. Doing so is necessary for successful registration.
Procedure
Step 1 |
Sign in to the customer view of https://admin.webex.com/login. |
||||
Step 2 |
In the left-hand navigation pane, under Services click Hybrid and then choose one:
The Webex cloud rejects any attempt at registration from the Expressway web interface. You must first register your Expressway through Control Hub, because the Control Hub needs to hand out a token to the Expressway to establish trust between premises and cloud, and complete the secure registration. |
||||
Step 3 |
Choose a method to register the Expressway-C:
|
||||
Step 4 |
Click Next, and for new registrations, click the link to open your Expressway-C. You can then sign in to load the Connector Management window. |
||||
Step 5 |
Decide how you want to update the Expressway-C trust list: A check box on the welcome page determines whether you will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Webex to add those certificates for you. Choose one of the following options:
|
||||
Step 6 |
Click Register. After you're redirected to Control Hub, read the on-screen text to confirm that Webex identified the correct Expressway-C. |
||||
Step 7 |
After you verify the information, click Allow to register the Expressway-C for Hybrid Services.
Troubleshooting Tips If registration fails and your on-premises environment proxies the outbound traffic, review the Before You Begin section of this procedure. If the registration process times out or fails (for example, you must fix certificate errors or enter proxy details), you can restart registration in Control Hub. |
Certificate Authorities for Hybrid Services
The table lists the Certificate Authorities that your on-premises or existing environment must trust when using Hybrid Services.
If you opted to have Webex manage the required certificates, then you do not need to manually append CA certificates to the Expressway-C trust list.
Note |
The issuers used to sign the Webex host certificates may change in future, and the table below may then be inaccurate. If you are manually managing the CA certificates, you must append the CA certificates of the issuing authorities that signed the currently valid certificates for the hosts listed below (and remove expired/revoked CA certificates). |
Cloud hosts signed by this CA |
Issuing CA |
Must be trusted by |
For this purpose |
---|---|---|---|
CDN |
O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root
|
Expressway-C |
To ensure Expressway downloads connectors from a trusted host |
Common identity service |
O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority
|
Windows Server 2003 or Windows Server 2008 hosting the Cisco directory connector Expressway-C |
To synchronize users from your Active Directory with Webex and to authenticate Hybrid Services users |
Webex App |
O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority
|
Expressway-C |