Netscape MANAGEMENT SYSTEM 6.0 Installation And Setup Manual page 56

System Overview
Table 1-2 Authentication plug-in modules for end-user enrollments
Plug-in module name
Manual authentication
Directory-based
authentication
Directory-based PIN
authentication
NIS-based authentication
Portal-style authentication
When you configure a Registration Manager or Certificate Manager an
authentication module, you can specify how the DN should be used to formulate
the subject name. As a result, neither the user nor the agent needs to figure out or
enter the subject name—its formulation is entirely automated.
You can also write custom authentication modules, for example to authenticate end
entities by using existing customer databases or security systems.
Tutorials and sample code provided as a part of CMS software development kit
(SDK) demonstrate how to write a custom authentication module. For details, see
section "CMS SDK" on page 65.
For information about ways customized authentication modules can be used
during enrollment, see "Some Enrollment Scenarios" on page 84.
56 Netscape Certificate Management System Installation and Setup Guide • March 2002
Description
Requires manual approval by an agent. This authentication module is
hardwired; you cannot configure it. This ensures that when the server
receives requests that lack authentication credentials, it sends them to the
request queue for agent approval. It also means that if you don't configure
Certificate Management System for any other authentication mechanism,
the server automatically sends all certificate-related requests to a queue
where they await agent approval.
Checks a user's name and password against the user's entry in a specified
directory and uses the DN for that entry to formulate the subject name for
the certificate.
Checks a user's name, password, and a special one-time PIN against the
user's entry in a specified directory and uses the DN for that entry to
formulate the subject name for the certificate. The PIN is stored in salted
and hashed form, and is removed after being used once to authenticate a
user during enrollment.
Authenticates end users based on their user IDs and passwords stored in a
NIS server. Optionally, uses an LDAP directory for formulating certificate
subject names.
Checks that a user's name is unique in an LDAP directory.