Skip to main content
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.
Untitled Diagram Drawio 2

​
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

​
1. 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.

​
2. 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.

​
3. Centralized Traffic Management

All SDK communication passes through a single controlled gateway, enabling better monitoring and traffic management.

​
4. 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