Workspace Weekly: Named Pipes for Custom Connectors

January 15, 2026

Custom Connectors allows you to model real-world digital workspace access paths that do not fit neatly into a built-in connector, making them the most powerful parts of Login Enterprise.

Until now, communication between a Custom Connector and the Launcher relied heavily on command-line arguments and indirect states, which made things harder to secure, monitor, and extend.

We are excited to share that Login Enterprise 6.4 has introduced Named Pipes for Custom Connectors, a new way for Custom Connectors and the Launcher to communicate directly and securely within a user session.

What’s new in 6.4

With Named Pipes, the Launcher and a Custom Connector establish a lightweight, bidirectional communication channel using Windows named pipes.

Instead of passing sensitive data through command-line arguments or relying on timeouts and heuristics, the connector and Launcher can exchange structured JSON messages in memory.

At a high level, this means:

• No credentials exposed in command lines or logs
• Immediate visibility into connection success, failure, and session lifecycle
• Cleaner session tracking with fewer assumptions
• A foundation for richer custom events and diagnostics

Below is a simplified view of how this works:

Why this matters to you

Imagine you are a platform team testing access to a remote system that uses a proprietary client, a custom authentication flow, or a nonstandard launch process. Historically, you may have relied on window title matching, process tracking, and timeouts to infer whether a session really started or ended.

With Named Pipes, your Custom Connector can explicitly tell the Launcher:

• The moment the remote session window is created
• Which process ID should be tracked
• When the connection fails and why
• When the session ends, even if the window was never tracked successfully

That means fewer false positives, faster failure detection, and clearer test results without waiting for timeouts to expire.

How it works at a high level

When a Launcher starts a Custom Connector session, it automatically creates a named pipe and exposes the pipe name to the connector through an environment variable. The connector connects to that pipe and receives a structured configuration message containing session details and credentials.

From there, the connector can send events back to the Launcher, such as: RemoteConnectionWindowCreated, RemoteConnectionFailure, RemoteConnectionWindowClosed, or custom informational events

All these events show up naturally in Login Enterprise session data, including the All Events page, without requiring separate API calls.

Built for flexibility

Named Pipe communication is optional. If an existing Custom Connector does not use it, everything continues to work exactly as before. However, for new connectors or updated ones, this offers a cleaner and more robust integration path.

To simplify adoption, the Launcher installer includes a Custom Connector SDK that handles pipe connection, message framing, and serialization for you. You can also implement the protocol manually, if you prefer full control.

Learn more and try it yourself

You can find full documentation here: Configuring Connectors and Connections: Named Pipes for Custom Connector

To help you get started, we will also be publishing a small, self-contained example repository that demonstrates a working Custom Connector using Named Pipes, including basic event reporting and session lifecycle handling: Custom Connector demo for Named Pipes

If you are already building or maintaining Custom Connectors, this is one of the most impactful improvements in Login Enterprise 6.4. It makes connectors easier to reason, debug, and trust when you are running automated testing at scale.

Thank you for your feedback on Login Enterprise 6.4 features

This is the last Workspace Weekly in the Login Enterprise 6.4 feature series. Thanks for all the feedback along the way, and if you build or update a custom connector using named pipes, send us what worked well and what you want next.

To set up a new appliance or update an existing one, go to Downloads. If your appliance already exists and is internet-connected, follow updating Login Enterprise, for additional update steps.

Don’t forget to take a snapshot first, and as always, thank you for your feedback!

Stay tuned for more Workspace Weekly feature spotlights, and join our Slack channel #workspace-weekly to share field stories, tips, and interesting finds.