PortalEnroll Plug-in ModuleChapter 1 Authentication Plug-in Modules 45m If the server fails to find a matching user name in the directory, it uses theregistration information to create a user entry for the new user and addrelevant attributes. The server also retrieves information required toconstruct the subject name for the certificate.If, for some reason, the directory to which the server binds for authenticatingthe user ID and password is unavailable, the server returns an LDAP errorcode and writes it to the log. A sample log entry with an LDAP error code isshown below:28/Jun/1999:18:40:25 -0700] conn=0 op=7 RESULT err=32 tag=101nentries=0 etime=0]3. Next, the server subjects the certificate request to policy processing. For details,see Chapter 18, “Setting Up Policies” of CMS Installation and Setup Guide.m If the request fails any of the configured policies, the server rejects therequest, logs an error message, and sends a rejection notification to the enduser. Note that if this happens, the user won’t be able to reregister usingthe same user name.m If the request passes all the configured policies, the server issues the enduser a certificate.The end user gets the certificate, which, if the server is configured to do so,is delivered to the email address specified in the request or in the directory;for information on configuring a Certificate Manager or RegistrationManager to send automated notifications, see section “Notifications ofCertificate Issuance to End Entities” in Chapter 16, “Setting Up AutomatedNotifications” of CMS Installation and Setup Guide.Configuration Parameters of PortalAuthIn the configuration file, the PortalEnroll module is identified asauths.impl.PortalEnroll.class=com.netscape.cms.authentication.PortalEnroll.In the CMS window, the module is identified as PortalEnroll. Figure 1-9 showshow configurable parameters for the module are displayed in the CMS window.
