Remote mapping
Save an authorized Pub shared with you, then open it on a local loopback port so existing tools can use it through a familiar localhost address.
Before you begin
The source publication must be running. The receiving computer needs Pubto Desktop and the shared Pub address. Database credentials remain in the database client.
Shortest path
Desktop → My Subscribe → Add Pub → Create local mappingSave the shared Pub
Add the HTTP, HTTPS, WS, WSS, or TCP Pub address to My Subscribe. Pubto detects its transport and keeps the saved address separate from your own publications.
Connect existing tools
Create a Local Mapping from that subscription, then point the browser, API client, database GUI, CLI, or development process at the local listener. Test the mapping before relying on it.
Treat databases as sensitive
Use service-level credentials and TLS where supported, limit the audience, choose a short duration, and remove the mapping and saved Pub as soon as the authorized session ends.
Before you share
- The target owner authorized the connection
- The Pub is saved in My Subscribe
- The local listener uses loopback
- The application still requires its own credentials
- The subscription and mapping are removed after use
The current standalone CLI does not create local mappings; use Desktop or the Agent API described by the managed Skill.