Webapp Gateway
The Adeptia Webapp Gateway is the single entry point through which all requests to the Adeptia platform's web interface and services flow, providing centralized routing, authentication enforcement, and request control before any request reaches the underlying platform services.
What the gateway does
Every request a user or integration client makes to the Adeptia platform passes through the gateway. The gateway evaluates each request and decides whether to forward it, reject it, or transform it before it reaches its destination. This means security and routing logic is applied consistently, regardless of which part of the platform is being accessed.
Authentication enforcement
Before forwarding any request, the gateway verifies that the request carries a valid session. Requests that arrive without a recognized session credential are rejected immediately with an authorization error and never reach the platform services behind the gateway.
Request routing and host resolution
The gateway routes incoming requests to the appropriate internal service based on the request path and, where applicable, information supplied by the caller. It also supports dynamic host resolution, allowing the destination of a request to be determined at runtime from information provided in the request itself, rather than being fixed at configuration time. This gives the platform flexibility in multi-instance and distributed deployments.
HTTP method restrictions
The gateway can be configured to block specific HTTP methods on particular routes. Requests using a disallowed method are rejected with a clear error before they reach any service, reducing the platform's exposure to unintended or unsafe operations.
Health and operational visibility
The gateway provides a health-checking capability that aggregates status information across the running instances of platform services. Administrators can query the health of a named deployment and receive a consolidated view of which instances are up or down.
Response header control
The gateway can strip specific response headers returned by downstream services before those responses are sent back to the caller. This allows the platform to control exactly what metadata is exposed to clients, independent of what individual services return.
Version control coordination
When a version control maintenance operation is initiated, the gateway coordinates the action across all running service instances concurrently rather than targeting only a single instance. This ensures that the operation is dispatched to all instances before the primary request is processed.
Why it matters for customers
Because all traffic passes through a single gateway, customers benefit from:
| Benefit | What it means in practice |
|---|---|
| Simplified access | One entry point for the entire platform, regardless of how many services run behind it |
| Operational visibility | Health status across all instances is available in one place |
| Controlled exposure | Response content and allowed operations are governed centrally, not per service |
| Reliable coordination | Multi-instance operations are dispatched concurrently across all running instances |