Workspace Weekly: Custom Events for Launchers and Connectors in Login Enterprise

September 25, 2025

Get a quick AI summary ChatGPT | Perplexity | Claude | Google AI Mode

Our Workspace Weekly series is about practical value you can use today. This edition spotlights Custom Events for Launcher and Connectors, which now appear directly in the Login Enterprise Events web interface! In short, your connector can emit simple, session-aware messages that show up right where your team already looks for answers. That means faster troubleshooting, less tool switching, and clearer timelines during incidents.

What’s new

Custom events are user-defined messages that your connector sends during a Test. Each event includes a timestamp, a session ID, and a message. They appear alongside standard Launcher and test events in three places in the Login Enterprise web interface: the Events tab for a test run, the Dashboard tile for the test and its Events, and the global Events section of the Appliance UI. These events are informational and do not change execution or scoring.

Try it out!

1. Confirm you are on Login Enterprise 6.2 or later.
2. In your custom connector, call the emission API to send an event. The sessionId is passed to the connector during initialization so your event is associated with the correct run.
3. Start a test, then open the Events tab to see your message appear.

Notes and considerations

• Keep messages concise and descriptive.
• Custom events follow the same retry/buffering logic as standard events, so transient network issues don’t silently drop messages.
• If a Launcher is older than 6.2, custom events won’t be available until it’s upgraded.

Imagine if…

1. You’re chasing an intermittent login failure. Emit events at Auth Start, Token Refresh, Resource Selected. When a run fails, you immediately see the last successful checkpoint and what happened next.
2. A connector uses conditional logic. Emit which branch was chosen and why. Reproducing a customer issue becomes a two-minute task instead of a multi-hour guess.
3. A site sees occasional 502 responses from a gateway. Emit a warning with retry counts. Later, correlate these warnings with EUX dips and a hypervisor spike to pinpoint root cause.
4. You roll out Seamless Mode for Citrix published apps. Emit a one-line confirmation that the connector launched with expected flags – audits become simple and repeatable.
5. Your CI pipeline runs pre-prod validation. Use the Public API to post “deploy started” and “deploy finished” next to test results for a clean operational timeline.

Recommended message style

Adopt a compact, scannable prefix so teams can filter quickly, like:

COMPONENT|SEVERITY|CODE – short message

Such as:

CONNECTOR | INFO | ResourceSelected – app=Excel

Of course, the message style is up to you, so if you already have a message style at your organization you can still follow it.

See it in action

• Demo repository: LoginEnterprise-CustomEvents-Demo
• Docs: Configuring Connectors and Connections:  Custom Events for Connectors and Launchers & Passing Session ID to the Custom Connector

Click to View Details

Figure 1: Events feed with custom connector messages.

Wrap up

Custom connector events give you a lightweight way to tell the story of each session inside the appliance. Use them at key checkpoints, avoid verbosity, and you’ll cut time to root cause while creating cleaner timelines for audits and postmortems.

Join the conversation in #workspace-weekly (Slack) and share your first impressions and screenshots.

Stay tuned for more Workspace Weeklies!