...
Security Manager Control Command Shell allows Masters Users to administer and monitory monitor Security Manager.
Security Manager has 8 subsystems to handle requests from its own components and PKI-enabled products,
Communication
- Public-Key Infrastructure X.509 - Certificate Management Protocal (PKIX-CMP) subsystem - manage keys and defaults to 2 processes
- Entrust proto-PKIX (SEP) subsystem - Entrust proprietary and handles requests from apps such as Entrust Authority Enrollment Server for Web, 2 processes, can safely disable if not using
Prior to Security Manager 8.1, the Entrust proto-PKIX subsystem handled
both the proto-PKIX and SEP (Secure Exchange Protocol) protocols. Secure
Exchange Protocol is no longer supported and the SEP subsystem now only
supports proto-PKIX. - Administration Service Handler (ASH) subsystem - handles requests from SMA, defaults to 4 processes
- XML Administration Protocol (XAP) subsystem - proprietary and used by clients such as Entrust Admin Services, defaults to 2 processes
Internal Functions
- Key Generator subsystem
- Automatic Backup subsystem
- Database Integrity Check subsystem
- CRL and Maintenance subsystem
See Security Manager 8.1 Deployment Guide document issue 3.0 for more details.
Security Manager Database
Store information about the PKI users and the infrastructure in the database. SM encrypts and protects data using keys derived from the Master User password. The database is used to,
...