Securing the Connection with Novell Audit631novdocx (en) 11 July 20086Securing the Connection withNovell AuditNovell ® Audit utilizes SSL certificates to ensure that communications between a loggingapplication and the Secure Logging Server are secure. By default, the Secure Logging Serverutilizes an embedded root certificate generated by an internal Novell Audit Certificate Authority(CA). Also, by default, the Identity Manager Instrumentation utilizes a public certificate that issigned by the Secure Logging Server root certificate. You can, however, configure Novell Audit touse certificates generated by an external CA.The following sections review how to use custom certificates to secure the connection betweenIdentity Manager and Novell Audit: Section 6.1, “Updating the Novell Audit Certificate Infrastructure,” on page 31 Section 6.2, “The Novell Audit AudCGen Utility,” on page 32 Section 6.3, “Creating a Root Certificate for the Secure Logging Server,” on page 35 Section 6.4, “Creating Logging Application Certificates,” on page 36 Section 6.5, “Validating Certificates,” on page 37 Section 6.6, “Securing Custom Certificates,” on page 376.1 Updating the Novell Audit CertificateInfrastructureYou can change the internal Novell Audit CA and embedded product certificates to certificatessigned by your enterprise CA so you can integrate Novell Audit with your enterprise securityinfrastructure.WARNING: Although the process of using certificates signed by external CAs is relatively simple,the consequences of failing to change all required components are serious. Logging applicationsmight fail to communicate with your Secure Logging Server, so events are not recorded.To update your Novell Audit certificate infrastructure with a custom certificate:1 Identify all Secure Logging Servers and Identity Manager servers where certificates arelocated.2 Use AudCGen to generate a CSR for the Secure Logging Server.For information on generating a CSR with AudCGen, see “Creating Logging ApplicationCertificates” on page 36.3 Have the CSR signed by your enterprise CA.If necessary, convert the returned certificate to a Base64-encoded .pem file.4 Shut down all Secure Logging Servers and Identity Manager servers.5 Delete and purge all application cache (lcache) files.