Binding a TLS server profile to a gateway service

You can bind the SSL certificate of a TLS profile to a gateway service to establish an HTTPS binding. This enables you to access the service by using the HTTPS communication protocol.

Before you begin

One of the following roles is required:

  • Administrator
  • Owner
  • Topology Administrator
  • Custom role with the Topology: Manage permissions
For more information on which user roles have access, see Adding members to the admin organization.

About this task

Perform the following steps to bind a TLS profile to a gateway service.

Procedure

  1. In the Cloud Manager user interface, click TopologyTopology, then select the gateway service that you want to work with.
  2. Scroll down to the API Invocation Endpoint section, and under Server Name Indication (SNI) select the required TLS server profile.

    You can also bind a TLS server profile during the initial registration of a gateway service; see Registering a gateway service.

  3. Click Save when done.

Results

The TLS profile binds to the gateway service.

What to do next

If you want to change the TLS Profile from Cloud Manager, for SNI Mapping of API Invocation endpoint, it is automatically changed in the associated Gateway. You do not need to do a removal or re-registration of the Gateway service.