4.3 Named Pipes Configuration

Secure local communication between proxy and gateway.

Why Named Pipes?

  • No network overhead
  • No additional ports
  • Windows security integrated
  • ACL-based access control

Gateway Configuration

In appsettings.json:

{
  "Kestrel": {
    "Endpoints": {
      "NamedPipe": {
        "Url": "http://pipe:DataGatewayApi"
      }
    }
  }
}

Permissions

The Named Pipe must be accessible to the proxy service:

# Set ACL for Named Pipe (in Gateway code)
# Only SYSTEM and Proxy Service Account

Proxy-Side Configuration

{
  "Target": {
    "Type": "NamedPipe",
    "PipeName": "DataGatewayApi",
    "ConnectionTimeout": 5000,
    "ReadTimeout": 30000
  }
}

Monitoring

# Check pipe status
Get-ChildItem \\.\pipe\ | Where-Object { $_.Name -like "*DataGateway*" }
Zuletzt geändert: on 2026/01/29 at 11:21 PM