Understand the connection before you publish an application.
Updated 6 September 2026
The connection model
Your connector opens a WebSocket connection over TLS to PDF Access Cloud. A visitor’s HTTPS request terminates at the relay, then travels over the connector connection to your local HTTP app. The relay can process the contents of requests and responses. This is encrypted transport, not end-to-end encryption between visitor and local app.
Authentication and credentials
Passwords use salted scrypt hashing. Sign-in sessions use HTTP-only, host-only cookies. API credentials are random, stored as hashes and individually revocable. Each tunnel has a separate connector token. Rotating that token invalidates the previous token and disconnects the active connector.
Isolation
Public apps are served beneath a separate tunnel hostname. Dashboard cookies are host-only and are not sent to tunnel hosts. Account ownership is checked for tunnel and key operations. The default connector forwards only to the local loopback address and does not follow upstream redirects itself.
Defensive limits
The service bounds HTTP body size, request duration, concurrent requests and connector message size. Registration, sign-in and API requests are rate limited. It does not provide a global CDN, web application firewall, independent security certification or a DDoS protection guarantee.
Before sharing
Require authentication in your app for private content. Turn off debug consoles, admin tools and development routes you do not intend to expose. Keep the connector token in an environment variable, separate from source control. Review the downloaded connector before running it. Stop a tunnel or rotate its token if anything appears wrong.