Console de surveillance WebADM : Arrêtez de chercher et commencez à surveiller

Authentication infrastructure has a talent for being invisible, right up until a connector goes down, a backend slows to a crawl, or failed logins begin appearing from somewhere unexpected.

At that point, nobody wants a scavenger hunt through status pages, log files and browser tabs.

Le mode Console de surveillance WebADM changes that. It brings live authentication activity, platform health, connector availability, logs, alerts, license consumption, system counters and service performance into one centralized dashboard.

The console became available with WebADM 2.4.17. It then received major enhancements in version 2.4.18 and further user-interface improvements in version 2.4.19. In other words, it did not simply arrive, it quickly got sharper.

Mission control for your WebADM environment

The Monitoring Console provides an at-a-glance view of what is happening across WebADM and refreshes the information live. Think of it as mission control, minus the dramatic countdown and the complicated swivel chairs.

From a single page, administrators can:

• Follow authentication activity across integrated systems.
• Review product license usage and capacity.
• Check the availability of configured connectors.
• See recent authentication logs and active alerts.
• Track operational counters for WebADM services.
• Monitor latency and throughput for key services and storage backends.

That means less time asking, “Which screen was that on?” and more time understanding what the platform is actually doing.

See authentication in motion

Authentication events are much easier to understand when they are not buried inside a wall of text.

The console’s Network view visualizes the relationships between authentication sources and targets. It provides a live picture of how requests are moving through the environment, helping administrators understand which systems are communicating with WebADM and where requests are being processed.

Switch to the Geo view, and login sources can be plotted on a world map. This makes unusual geographic activity considerably easier to notice than it would be in a traditional log entry.

One important detail: the map is useful, but it is not psychic. Source IP addresses must be correctly forwarded to OpenOTP by the integrated client systems, and live activity requires an appropriate Client Policy for each integrated system.

Logs that tell the whole story

The live log panel displays recent authentication events together with the details administrators need for investigation: timestamp, status, application, user, client, server, source IP and target.

Successful and failed requests can therefore be reviewed directly alongside the rest of the platform telemetry. No separate log-file expedition required.

The console also displays active security and platform alerts. When everything is behaving, the alert panel remains pleasantly uneventful. When something needs attention, administrators can immediately see the relevant application, message, server and network context.

Find the weak link before it becomes an outage

WebADM environments can depend on several connected services. The Monitoring Console displays up-or-down status indicators for configured:

• Session Servers
• LDAP directories
• SQL databases
• SMTP services
• PKI services
• Proxy connectors

Green is reassuring. Red is actionable. Both are more useful than guessing.

The console also provides latency and throughput statistics for OpenOTP and SpanKey services, as well as LDAP and SQL storage backends. This makes it easier to see whether a service is responding normally, a backend is slowing down or a connector has become unavailable.

Keep an eye on capacity, and everything else

Le mode Product Licenses section displays current consumption against available capacity for WebADM products such as OpenOTP and SpanKey. Administrators can see how much of each license is in use without reaching for a spreadsheet or waiting for a capacity surprise at the least convenient moment.

Le mode System Statistics section provides counters for activity across the platform, including certificates, electronic signatures, electronic seals, mobile push notifications, SMS messages, user badging and AI reports.

It is a compact way to understand not only whether WebADM is running, but how it is being used.

Easy to reach, carefully protected

Administrators can open the Monitoring Console from the Surveillance tab in the WebADM Administrator Portal. It can also be reached directly through the dedicated /console/index.html endpoint.

Direct access does not require a session in the Administrator Portal, but it does require a valid console authentication token before the live Server-Sent Events stream is established.

The console is disabled by default. To enable it, an administrator must configure the console_tokens directive in /opt/webadm/conf/webadm.conf and restart WebADM. Multiple tokens can be configured when more than one console needs access.

This access model is deliberately explicit because the dashboard can display sensitive operational information, including usernames, authentication activity, source IP addresses, geolocation and platform metrics.

Console tokens should therefore be treated like secrets, rotated periodically and replaced whenever an operator who knew a token leaves the organization. Access to /console/* should also be limited to trusted administrators and management networks.

A monitoring console should increase visibility, not become public entertainment.

Pour commencer

Enabling the console takes only a few steps:

1. Run WebADM 2.4.17 or later.
2. Generate a strong random token, for example with openssl rand -hex 16.
3. Add the token to the console_tokens directive in webadm.conf.
4. Restart WebADM.
5. Open the Monitoring tab, or the direct console URL, and connect.

The complete configuration procedure, including support for multiple tokens and both WebADM restart methods, is available in the RCDevs technical documentation.

Your WebADM environment already has a pulse. Now you can see it.

The WebADM Monitoring Console gives security and operations teams a clearer view of authentication traffic, platform health, infrastructure dependencies, license capacity and backend performance.

Whether you are investigating a failed login, checking LDAP responsiveness, reviewing an alert or simply confirming that everything is running smoothly, the information is already there, live and on one screen.

No tab safari. No log archaeology. Just a better view of WebADM.

Ready to see your environment in real time? Explore the WebADM Monitoring Console, follow the technical setup guide or contact RCDevs to request a free proof of concept.