====== 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'':

<code javascript>
{
  "Kestrel": {
    "Endpoints": {
      "NamedPipe": {
        "Url": "http://pipe:DataGatewayApi"
      }
    }
  }
}
</code>

===== Permissions =====

The Named Pipe must be accessible to the proxy service:

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

===== Proxy-Side Configuration =====

<code javascript>
{
  "Target": {
    "Type": "NamedPipe",
    "PipeName": "DataGatewayApi",
    "ConnectionTimeout": 5000,
    "ReadTimeout": 30000
  }
}
</code>

===== Monitoring =====

<code powershell>
# Check pipe status
Get-ChildItem \\.\pipe\ | Where-Object { $_.Name -like "*DataGateway*" }
</code>