Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Omni Gateway: Enable Last Mile Security for Managed Omni Gateway in RTF

Publish Date: Jul 3, 2026
Prerequisite(s)
Ingress Configuration: Last Mile security encrypts HTTP traffic between your Ingress controller and the application pod. You must configure your Ingress controller to forward traffic via HTTPS to the upstream gateway pods. This requires modifying your RTF Ingress template according to your specific Ingress controller configuration.
Task

Once the Ingress configuration is complete, apply the following PolicyBinding configuration to your Kubernetes cluster to enable the inbound TLS policy.

 

apiVersion: gateway.mulesoft.com/v1alpha1
kind: PolicyBinding
metadata:
  name: "omnigateway-lms-tls-inbound"                  // You can name this as per your setup
  labels:
    rtf.mulesoft.com/target-id: <Enter Your Omnigateway Target id>     //You can get this by describing your Omnigateway deployment manifest
  namespace: <RTF APP Namespace>               // Make sure you are adding the RTF app namesapce here
spec:
  targetRef:
    kind: Selector
    selector:
      kind: ApiInstance
      labels:
        flex.mulesoft.com/organization-id: "<Replace With Your OrgID>"
        flex.mulesoft.com/environment-id: "<Replace With Your Env Id>"
  policyRef:
    name: tls-inbound
  config:
    certificate:
      crt: |
        -----BEGIN CERTIFICATE-----
        
        -----END CERTIFICATE-----
      key: |
        -----BEGIN PRIVATE KEY-----
        
        -----END PRIVATE KEY-----

 

Steps

After applying the configuration, restart the gateway:

  • Navigate to Runtime Manager > Omnigateway Gateway.

  • Select your gateway.

  • Click Stop gateway, then click Start gateway.

If you are facing any issues, Please open the Mulesoft Support Case.

Knowledge Article Number

005388366

 
Loading
Salesforce Help | Article