Managing Authentication Plug-Ins - Red Hat CERTIFICATE SYSTEM 7.2 - ADMINISTRATION Administration Manual

Do not interrupt the key-generation process. Upon completion of the key generation, the request
is submitted to the server to issue the certificate. The server subjects the request to the certificate
profile and issues the certificate only if the request meets all the requirements.
When the certificate is issued, install the certificate in the browser.
6. Verify that the certificate is installed in the browser's certificate database.
7. If directory- or PIN-based authentication was configured with PIN removal, re-enroll for another
certificate using the same PIN. The request should be rejected.

15.7. Managing Authentication Plug-ins

Custom authentication plug-in modules can be registered through the CA Console. Authentication
plug-in modules can also be deleted through the CA Console. Before deleting a module, delete
instances that are based on that module.
To register or delete a module, do the following:
1. Log into the Console.
pkiconsole https://server.example.com:9443/ca
2. In the Configuration tab, click Authentication in the navigation tree
3. In the right pane, click the Authentication Plug-in Registration tab.
The tab lists modules that are already registered.
4. To delete a registered module, select that module, and click Delete.
5. To register a plug-in, click Register.
The Register Authentication Plug-in Implementation window appears.
6. Specify which module to register by filling in the two fields:
• Plugin name. The name for the module.
• Class name. The full name of the class for this module. This is the path to the implementing
Java™ class. If this class is part of a package, include the package name. For example, to
register a class named customAuth in a package named com.customplugins, the class
name is com.customplugins.customAuth.
7. Click OK.
Managing Authentication Plug-ins
355