By default, you access the [New Edge UI](https://docs.apigee.com/private-cloud/v4.54.00/new-edge-ui) over HTTP by using the IP address or DNS name of the New Edge UI node and port 3001. For example: ``` http://edge_UI_IP:3001 ``` Alternatively, you can configure TLS access to the New Edge UI so that you can access it in the form: ``` https://edge_UI_IP:3001 ``` > [!NOTE] > **NOTE:** The New Edge UI uses the same port for HTTPS and HTTP. That means you cannot access the New Edge UI using both HTTP and HTTPS concurrently. ## TLS requirements The New Edge UI supports TLS v1.2 and higher. If you enable TLS on the New Edge UI, users must connect to the New Edge UI using a browser compatible with TLS v1.2 or higher. ## TLS configuration properties Execute the following command to configure TLS for the New Edge UI: ``` /opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure-ssl -f configFile ``` Where configFile is the config file that you used to install or configure the New Edge UI. Before you execute this command, you must edit the config file to set the necessary properties that control TLS. The following table describes the properties that you use to configure TLS for the New Edge UI: | Property | Description | Required? | |---|---|---| | `MANAGEMENT_UI_SCHEME` | Sets the protocol, "http" or "https", used to access the New Edge UI. The default value is "http". Set it to "https" to enable TLS: ``` MANAGEMENT_UI_SCHEME=https ``` | Yes | | `MANAGEMENT_UI_TLS_OFFLOAD` | If "n", specifies that TLS requests to the New Edge UI are terminated at the New Edge UI. You must set `MANAGEMENT_UI_TLS_KEY_FILE` and `MANAGEMENT_UI_TLS_CERT_FILE`. If "y", specifies that TLS requests to the New Edge UI are terminated on a load balancer, and that the load balancer then forwards the request to the New Edge UI by using HTTP. If you terminate TLS on the load balancer, the New Edge UI still needs to be aware that the original request came in over TLS. For example, some cookies have a Secure flag set. You must set `MANAGEMENT_UI_SCHEME` to "https" or else `MANAGEMENT_UI_TLS_OFFLOAD` is ignored: ``` MANAGEMENT_UI_SCHEME=https MANAGEMENT_UI_TLS_OFFLOAD=y ``` | Yes | | `MANAGEMENT_UI_TLS_KEY_FILE` `MANAGEMENT_UI_TLS_CERT_FILE` | If `MANAGEMENT_UI_TLS_OFFLOAD=n`, specifies the absolute path to the TLS key and cert files. The files must be formatted as PEM files with no passphrase, and must be owned by the "apigee" user. The recommended location for these files is: ``` /opt/apigee/customer/application/edge-management-ui ``` If that directory does not exist, create it. If `MANAGEMENT_UI_TLS_OFFLOAD=y`, then omit `MANAGEMENT_UI_TLS_KEY_FILE` and `MANAGEMENT_UI_TLS_CERT_FILE`. They are ignored because requests to the New Edge UI come in over HTTP. | Yes if `MANAGEMENT_UI_TLS_OFFLOAD=n` | | `MANAGEMENT_UI_PUBLIC_URIS` | If `MANAGEMENT_UI_TLS_OFFLOAD=n`, specifies the URL of the New Edge UI. Set this property based on other properties in the config file. For example: ``` MANAGEMENT_UI_PUBLIC_URIS=$MANAGEMENT_UI_SCHEME://$MANAGEMENT_UI_IP:$MANAGEMENT_UI_PORT ``` Where: - MANAGEMENT_UI_SCHEME specifies the protocol, "http" or "https", as described above. - MANAGEMENT_UI_IP specifies the IP address or DNS name of the New Edge UI. - MANAGEMENT_UI_PORT specifies the port used by the New Edge UI. See [Configure the New Edge UI](https://docs.apigee.com/private-cloud/v4.54.00/install-new-edge-ui) for more on these properties. If `MANAGEMENT_UI_TLS_OFFLOAD=y`: - `MANAGEMENT_UI_IP` specifies the IP address or DNS name of the *load balancer* , *not* of the New Edge UI. - The load balancer and the New Edge UI *must* use the same port number for requests, for example 3001. Use `MANAGEMENT_UI_PORT` to specify the port number on the load balancer and on the New Edge UI. | Yes | | `MANAGEMENT_UI_TLS_ALLOWED_CIPHERS` | Defines the list of available TLS ciphers as a comma-separated or space-separated string. Comma-separated string: ``` MANAGEMENT_UI_TLS_ALLOWED_CIPHERS=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ``` Space-separated string enclosed in double quotes: ``` MANAGEMENT_UI_TLS_ALLOWED_CIPHERS="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256" ``` | | ## Configure TLS To configure TLS access to the New Edge UI: 1. Generate the TLS cert and key as PEM files with no passphrase. For example: ``` mykey.pem mycert.pem ``` There are many ways to generate a TLS cert and key. For example, you can execute the following command to generate an unsigned cert and key: ``` openssl req -x509 -newkey rsa:4096 -keyout mykey.pem -out mycert.pem -days 365 -nodes -subj '/CN=localhost' ``` > [!NOTE] > **Note:**You do not typically use an unsigned cert and key in a production environment. 2. Copy the key and cert files to the `/opt/apigee/customer/application/edge-management-ui` directory. If that directory does not exist, create it. 3. Make sure the cert and key are owned by the "apigee" user: ``` chown apigee:apigee /opt/apigee/customer/application/edge-management-ui/*.pem ``` 4. Edit the config file that you used to install the New Edge UI to set the following [TLS properties](https://docs.apigee.com/private-cloud/v4.54.00/configuring-tls-ue#tls-props): > [!NOTE] > **Note:**When enabling TLS, you must pass the complete config file that you used to install the New Edge UI. ``` # Set to https to enable TLS. MANAGEMENT_UI_SCHEME=https # Do NOT terminate TLS on a load balancer. MANAGEMENT_UI_TLS_OFFLOAD=n # Specify the key and cert. MANAGEMENT_UI_TLS_KEY_FILE=/opt/apigee/customer/application/edge-management-ui/mykey.pem MANAGEMENT_UI_TLS_CERT_FILE=/opt/apigee/customer/application/edge-management-ui/mycert.pem # Leave these properties set to the same values as when you installed the New Edge UI: MANAGEMENT_UI_PUBLIC_URIS=$MANAGEMENT_UI_SCHEME://$MANAGEMENT_UI_IP:$MANAGEMENT_UI_PORT ``` 5. Execute the following command to configure TLS: ``` /opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure-ssl -f configFile ``` Where configFile is the name of the config file. The script restarts the New Edge UI. After the restart, the New Edge UI supports access over HTTPS. If you cannot log in to the New Edge UI after enabling TLS, clear the browser cache and try logging in again. ## Configure the New Edge UI when TLS terminates on the load balancer If you have a load balancer that forwards requests to the New Edge UI, you might choose to terminate the TLS connection on the load balancer, and then have the load balancer forward requests to the New Edge UI over HTTP: ![Architecture diagram showing TLS termination on a load balancer forwarding HTTP requests to the New Edge UI (edge-management-ui) on port 3001](https://docs.apigee.com/static/private-cloud/images/tls_edge_ui_lb-45400.png) This configuration is supported but you need to configure the load balancer and the New Edge UI accordingly. To configure the New Edge UI when TLS terminates on the load balancer: 1. Edit the config file that you used to install the New Edge UI to set the following [TLS properties](https://docs.apigee.com/private-cloud/v4.54.00/configuring-tls-ue#tls-props): > [!NOTE] > **NOTE:** When enabling TLS, you must pass the complete config file that you used to install the New Edge UI. ``` # Set to https to enable TLS MANAGEMENT_UI_SCHEME=https # Terminate TLS on a load balancer MANAGEMENT_UI_TLS_OFFLOAD=y # Set to the IP address or DNS name of the load balancer. MANAGEMENT_UI_IP=LB_IP_DNS # Set to the port number for the load balancer and New Edge UI. # The load balancer and the New Edge UI must use the same port number. MANAGEMENT_UI_PORT=3001 # Leave these properties set to the same values as when you installed the New Edge UI: MANAGEMENT_UI_PUBLIC_URIS=$MANAGEMENT_UI_SCHEME://$MANAGEMENT_UI_IP:$MANAGEMENT_UI_PORT ``` If you set `MANAGEMENT_UI_TLS_OFFLOAD=y`, omit `MANAGEMENT_UI_TLS_KEY_FILE` and `MANAGEMENT_UI_TLS_CERT_FILE`. They are ignored because requests to the New Edge UI come in over HTTP. 2. Execute the following command to configure TLS: ``` /opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure-ssl -f configFile ``` Where configFile is the name of the config file. The script restarts the New Edge UI. After the restart, the New Edge UI supports access over HTTPS through the load balancer. If you cannot log in to the New Edge UI after enabling TLS, clear the browser cache and try logging in again. ## Disable TLS on the New Edge UI To disable TLS on the New Edge UI: 1. Edit the config file that you used to install the New Edge UI to set the following [TLS property](https://docs.apigee.com/private-cloud/v4.54.00/configuring-tls-ue#tls-props): > [!NOTE] > **NOTE:** When disabling TLS, you must pass the complete config file that you used to install the New Edge UI. ``` # Set to http to disable TLS. MANAGEMENT_UI_SCHEME=http # Only if you had terminated TLS on a load balancer, # reset to the IP address or DNS name of the New Edge UI. MANAGEMENT_UI_IP=edge_UI_IP_DNS ``` 2. Execute the following command to disable TLS: ``` /opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure-ssl -f configFile ``` Where configFile is the name of the config file. The script restarts the New Edge UI. You can now access the New Edge UI over HTTP. If you cannot log in to the New Edge UI after disabling TLS, clear the browser cache and try logging in again.