Managing Authentication Plug-ins
426
Netscape Certificate Management System Administrator’s Guide • February 2003
Upon receipt of a notification about the certificate issuance, install the
certificate in your browser.
6.
Verify that the certificate is installed in the browser’s certificate database; for
example, in Communicator you can open the Security Info window and verify
that the certificate is listed in there.
7.
If you’ve set up the directory- and PIN-based authentication with PIN
removal, reenroll for another certificate using the same PIN. Your request
should get rejected.
8.
If you’ve set up the portal enrollment, verify that an entry for the user is
created in the directory. For example, you can point your browser to the portal
directory and find out if an entry for the user for whom you requested the
certificate exists.
In the URL field, type
ldap://<hostname>:<port>/<base_dn>??sub?(uid=<user_id>)
,
substituting
<hostname>
with the fully qualified host name of the Directory
Server,
<port_number>
with the port number at which the Directory Server is
listening to authentication requests from the Certificate Manager
<base_dn>
with the DN to start searching for the user’s entry, and
<user_id>
with the ID
of the user for whom you requested the certificate.
For example, if the directory host name is
corpDirectory
, port number is
389
,
base DN is
O=example.com
, and user’s ID is
jdoe
, the URL would look like
this:
ldap://corpDirectory:389/O=example.com??sub?(uid=jdoe)
In the resulting page, look for the user’s credentials and verify that they match
what you specified in the enrollment form. If you’ve configured CMS to
publish certificates to the same directory (Chapter 15, “Publishing”), you will
be able to see the certificate-related information; it typically includes
information such as the owner of the certificate, the CA that has issued the
certificate, the serial number, the validity period, and the certificate fingerprint.
Managing Authentication Plug-ins
You can register custom authentication plug-in modules from the CMS window.
You can delete an authentication plug-in module that you no longer need by using
the CMS window. Before deleting a module, be sure to delete all the instances that
are based on this module.
To register or delete a module:
Содержание Certificate Management System 6.1
Страница 1: ...Administrator s Guide Netscape Certificate Management System Version6 1 February 2003...
Страница 28: ...Documentation 28 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 68: ...Support for Open Standards 68 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 82: ...Uninstalling CMS 82 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 166: ...How a Registration Manager Works 166 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 382: ...ACL Reference 382 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 566: ...Managing Policy Plug in Modules 566 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 710: ...1 3 Organization Security Policies 710 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 716: ...Object Identifiers 716 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 762: ...DNs in Certificate Management System 762 Netscape Certificate Management System Administrator s Guide February 2003...
Страница 794: ...Managing Certificates 794 Managing Servers with Netscape Console December 2001...
Страница 810: ...The SSL Handshake 810 Managing Servers with Netscape Console December 2001...
Страница 828: ...828 Netscape Certificate Management System Administrator s Guide February 2003...