Single Sign-On — Single Sign-On System
A Security Policy Manager and proxy server that control who reaches which element, with what commands, and record everything they do. Deployed at Mobilink.
How SSO works
A view of how work moves through Single Sign-On.
Product resources
The challenge
Teams looking at Single Sign-On usually face shared passwords, no audit trail and scattered administration. Engineers log in directly with credentials that are hard to control. It is difficult to prove who ran which command on which element. Access rights are managed separately on each system. Left alone, these problems slow people down and make results harder to prove.
Shared passwords
Engineers log in directly with credentials that are hard to control.
No audit trail
It is difficult to prove who ran which command on which element.
Scattered administration
Access rights are managed separately on each system.
What it does
Single Sign-On covers Security Policy Manager, Security Proxy Server, Flexible authentication, Command filtering, Video logging and NMS integration in one solution. Each capability below does a specific job, and together they follow the work from identify to record.
Security Policy Manager
Central policy for users and elements.
Security Proxy Server
Sessions pass through a controlled proxy.
Flexible authentication
Password, system-generated keys or RFID.
Command filtering
Per-element command and protocol filtering.
Video logging
Lossless differential PNG in HD, 256-colour or greyscale.
NMS integration
SNMP traps report events to your NMS.
How it works
Single Sign-On follows 5 clear steps. Users pass the configured authentication flow. From there, work moves through each stage until the final step: commands, video and internal logs are retained.
Log in
Users pass the configured authentication flow.
Check policy
The Policy Manager resolves allowed elements.
Open session
SSH, Telnet, FTP or GUI runs through the proxy.
Filter
Disallowed commands and protocols are blocked.
Audit
Commands, video and internal logs are retained.
Specifications
Key technical details for Single Sign-On.
| Authentication | Username/password, system-generated keys, RFID; three-way proximity, SMS and Active Directory flow |
|---|---|
| User stores | LDAP, internal database, or external Oracle, SQL Server, DB2 or Sybase |
| Session access | SSH, Telnet, FTP, GUI |
| Logging | Commands, video (lossless differential PNG), internal logs |
Outcomes
The result is a clearer way of working: proxy-controlled sessions, individual authentication, per-element filtering, command and video logs and recorded, auditable access. These are the changes teams should expect once Single Sign-On is part of daily operations.
Who it's for
Single Sign-On is designed for Security, Admins, Engineers and Vendors. Each group gets something different from it, as the cards below show.
Security
Central policy and full audit.
Admins
One place for access rights.
Engineers
One login to permitted elements.
Vendors
Controlled, recorded third-party access.
AI integrated
Single Sign-On integrates with the Exceleron AI Layer, on-prem or in the cloud, using RAG for grounded answers and MCP to connect tools and data.
Before and after
What changes for your team with SSO.
Before
- Direct element logins
- Shared credentials
- No command restrictions
- Partial logs
- Unrecorded vendor access
With SSO
- Proxy-controlled sessions
- Individual authentication
- Per-element filtering
- Command and video logs
- Recorded, auditable access
Technology explained
These are the technologies and formats Single Sign-On works with, explained in plain language.
- SSH
- Encrypted remote command-line access.
- Telnet
- Legacy remote command-line access, still found on older equipment.
- FTP
- File transfer to and from network elements.
- GUI
- Sessions on graphical management applications.
- LDAP
- Standard protocol for user directories.
- Oracle
- Oracle enterprise database.
- SQL Server
- Microsoft relational database.
- DB2
- IBM enterprise database.
- Sybase
- SAP Sybase enterprise database.
- RFID
- Proximity cards or tags used to identify a user.