Configure Multi-Site Collaboration to use asymmetric keys

All Multi-Site Collaboration sites must use the same key type. Asymmetric keys cannot be used unless all sites use asymmetric keys. To use asymmetric keys with Multi-Site, all sites must be running Teamcenter 14.3 or later. Each Multi-Site site has its own public-private key pair. Sites that communicate with each other must have their public keys deployed on the FSCs of both sites. Use the following steps to configure Multi-Site sites to use asymmetric keys. Procedure Export the public key from each site using the steps in Export the public key from Teamcenter to a keystore file in Convert sites that use symmetric keys to use asymmetric keys. Do this for each key needed for the sites to communicate. Send the public keystore files and passwords to the other sites. Use a secure method such as encrypted email or an encrypted file transfer mechanism to send the files and passwords to the other sites. At each site, use the following command from a Teamcenter command prompt to import each public key into the keystore file that is deployed with the FSC: Copy keygen -importpubkey -keystore p12_keystore_file -storepass key_pass -srckeystore src_key_file -srcstorepass src_key_pass Where: p12_keystore_file The file name of the .p12 file holding the public key being replaced. key_pass The password for the .p12 file holding the public key being replaced. src_key_file The file name of the .p12 file holding the new public key. src_key_pass The password for the .p12 file holding the new public key. Update the FMS primary configuration file (FSC_HOME/fmsmaster_fscid.xml) to reference the alias names of each site. See the steps in Deploy the keystore file on the FSC and update the FSC configuration in Convert sites that use symmetric keys to use asymmetric keys. Following is an example of an updated configuration file. Copy