---
schema_version: "1"
id: 2e118ecf3345f7ca7daae0977d2a6304405871e461a95148f4c2b52510d96118
title: Configuring Inbound TLS for Managed Omni Gateway
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/managed-inbound-tls-config.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/managed-inbound-tls-config
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d26100e8309b6912812e0dacccfcf67202b87a72c86dae67df10bd3b9b664150
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
---

# Configuring Inbound TLS for Managed Omni Gateway

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

For Managed Omni Gateway deployed on CloudHub 2.0, the CloudHub 2.0 space manages the inbound TLS.

To configure a TLS context for the private space you’re deploying your Managed Omni Gateway to, see
[Configuring Domains and Certificates (TLS Context) for a Private Space](https://docs.mulesoft.com/cloudhub-2/ps-config-domains).
You can’t edit the TLS context for a shared space.

Configuring a TLS context for your private space means all APIs deployed to Managed Omni Gateways in
the private space are HTTPS and secure.

To configure outbound TLS context, see
[Configuring Outbound TLS for Managed Omni Gateway](https://docs.mulesoft.com/gateway/1.13/managed-outbound-tls-config).