Pangolin, the open-source zero-trust remote access platform that combines reverse-proxy-style access with VPN-like connectivity, has released version 1.21.
The headline feature allows a Pangolin client and site connector on the same local network to discover each other and establish a direct peer-to-peer connection, keeping packets within the local network instead of sending traffic through the internet.
This significantly reduces connection latency and unnecessary network egress. Both the Pangolin client and site connector must be updated to version 1.21 for the new behavior to work. Older installations will continue using the previous connection path.
The release also expands Pangolin’s pending-site provisioning workflow. Resources created from a provisioning blueprint for a pending site are now marked as pending. They remain hidden from the main resources list and are disabled by default, preventing users from accessing them before an administrator approves the site.
Administrators can still inspect, edit, and temporarily enable these resources for testing. Approving the site clears the pending status and enables its associated resources, while rejecting it removes both the site and the pending resources created for it.
On top of that, Pangolin 1.21 introduces two additions related to share links and access tokens. Share links can now be tied to a specific user account. When the link or its access token is used, that user appears in the logs, and Pangolin forwards the identity through its Remote-* headers to upstream applications.
Access tokens can now create persistent sessions as well. After a token is supplied through a query parameter or request header, Pangolin can exchange it for a session cookie. This removes the need to include the token with every subsequent request, unlike the previous API-key-style behavior.
Finally, private resources can now be enabled or disabled without deleting them, including when managed through blueprints. Plus, the login page remembers the identity provider used during the previous login and highlights it the next time the user signs in.
For more details, see the announcement or refer to the changelog.
