Documentation Index
Fetch the complete documentation index at: https://docs.quepass.com/llms.txt
Use this file to discover all available pages before exploring further.
The Client Proxy Server is deployed within the client’s infrastructure and acts as a secure intermediary between the Quepass SDK and the Quepass platform.
Instead of connecting directly to the Quepass environment, all SDK requests are first routed through the client’s proxy infrastructure.
This architecture provides better security control, monitoring, and integration with existing enterprise network policies.
1. Communication Flow
The SDK communication follows this sequence:
Client App
- Integrates Quepass SDK
- SDK sends requests to Client Proxy / APIM
- Proxy forwards requests through approved network channels
- Requests reach the Quepass environment
This design ensures that the client maintains full control over outbound network traffic.
2. Key Responsibilities
a. Request Forwarding
The proxy server receives API requests from the SDK and forwards them securely to the Quepass platform.
This ensures that all communication follows the client’s controlled network path.
b. Network Security Enforcement
The proxy allows organizations to apply internal security policies such as firewall rules, monitoring, and access control before requests reach the Quepass environment.
c. Centralized Traffic Management
All SDK communication passes through a single controlled gateway, enabling better monitoring and traffic management.
d. Infrastructure Integration
Because the proxy is deployed inside the client environment, it can integrate with existing infrastructure such as:
- API gateways
- Network security systems
- Monitoring tools
- Enterprise traffic controls
3. Client Proxy Server Configuration
a. Machine Specifications
Minimum Requirements
| Component | Specification |
|---|
| vCPUs | 2 |
| RAM | 4 GB |
| Storage | 120 GB |
Recommended Requirements
| Component | Specification |
|---|
| vCPUs | 4 |
| RAM | 8 GB |
| Storage | 240 GB |
b. Recommended Proxy Services (Runs on Provisioned VM or Server)
The following reverse proxy solutions are recommended for deployment:
| Proxy Server | Description |
|---|
| Apache HTTP Server | Widely used web server and reverse proxy with strong module support. |
| NGINX | High-performance reverse proxy suitable for handling large traffic volumes. |
| HAProxy | Reliable load balancer and proxy for high availability environments. |
| Traefik | Modern proxy designed for cloud-native and containerized environments. |
c. Network Requirements
- Outbound HTTPS (Port 443) access to Quepass environment
- Static public IP (recommended for IP allowlisting)
- Firewall rules restricting traffic to approved endpoints
- TLS 1.2 or higher required
