Working with Key Manager

Manage keys, certificates, and policies using the web-based Teamcenter Key Manager Administration application. Key Manager Administration is a web service or daemon that, for security purposes, is not running by default. Use care when managing keys, certificates, and policies. Changes have broad impact, affecting users across the Teamcenter site. Starting the Key Manager administration application web service or daemon The process for starting the administration application is the same for the primary key manager server as it is for the secondary key manager server. On the appropriate machine, start the service or daemon as follows: Windows service: Start the Windows service using the Windows Services application. Its name has the following form: "Teamcenter Key Manager Admin Web " Linux daemon: From the server machine console, navigate to the Teamcenter Key Manager server installation directory: $INSTALL_DIR/KeyManagerServer/ Run: Copy key_manager_admin -start Though you can leave the web service or daemon running on the primary server, for security purposes, you may wish to just run it when you have an actual need to use Key Manager Administration. The administration web service or daemon must remain running on the secondary server. (As keys and policies cannot be changed on the secondary server, doing so is not a security risk.) Running the Key Manager Administration application Once the service or daemon is running, open the Teamcenter Key Manager Administration application by navigating to the following URL and entering the key manager administrator password: Copy https://: is the name of the machine on which the Teamcenter Key Manager Administration web service is running. is 8204 unless changed when providing the Key Manager Server Component settings. The password is the one specified in Deployment Center for Key Manager Administrator Password when providing the Key Manager Server Component settings. Note The first time you connect to the Key Manager Administration application, your browser may not authorize the self-signed CA Root certificate generated during the Key Manager installation. If so, follow your browser's specific steps for adding the security certificate to its store of trusted Root Certificate Authorities. These steps typically involve viewing the self-signed certificate, copying or exporting the certificate to a file, and then importing that certificate to your trusted Root Certificate Authorities store. Once you have signed in, the Key Manager Administration application opens to the Policies tab as shown in the following example: