LogoLogo
umh-core
umh-core
  • Introduction
  • Getting Started
  • Usage
    • Unified Namespace
      • Overview
      • Payload Formats
      • Topic Convention
      • Producing Data
      • Consuming Data
    • Data Flows
      • Overview
      • Bridges
      • Stand-alone Flow
      • Stream Processor 🚧
    • Data Modeling 🚧
      • Data Models 🚧
      • Data Contracts 🚧
      • Stream Processors 🚧
  • Production
    • Updating
    • Sizing Guide
    • Corporate Firewalls
    • Metrics
    • Migration from Classic
  • Reference
    • Configuration Reference
    • Container Layout
    • State Machines
    • Environment Variables
  • UMH Core vs UMH Classic
  • UMH Classic
    • Go To Documentation
  • Ressources
    • Website
    • Blog
Powered by GitBook
On this page
  1. Production

Corporate Firewalls

If you're behind a corporate firewall that performs TLS inspection (MITM), you might see certificate errors. In this case, you can:

  1. Recommended: Add your corporate CA certificate to the container's trusted certificates

  2. Last Resort: Set allowInsecureTLS: true in your config:

agent:
  communicator:
    allowInsecureTLS: true  # WARNING: Only use if corporate firewall blocks secure connections

⚠️ Security Warning: The allowInsecureTLS option disables certificate validation. Only use this if:

  • You're behind a corporate firewall that you trust

  • You cannot add your corporate CA certificate

  • You understand the security implications

PreviousSizing GuideNextMetrics

Last updated 8 days ago