Asymmetric keys and FMS

By default, FMS uses symmetric keys for ticket validation. A typical symmetric key scenario has the Teamcenter server generating the ticket and signing it with the symmetric key. That ticket is then sent to FMS where it is validated using the same symmetric key deployed on the FMS side. Symmetric passwords and keys are stored in the Teamcenter vault when FMS has been installed using Deployment Center. You can optionally configure your site to use more secure public-private (asymmetric) key pairs. When setting up your sites and choosing to use asymmetric keys, Deployment Center generates the public-private key pair during deployment. The private key resides with the Teamcenter server, and the public key is deployed with the FSC. The Teamcenter server uses the private key to sign the ticket. The FSC then uses the public key to validate the signature on the ticket that is sent when uploading or downloading a file. Be aware that FSC administrative commands continue to use a symmetric key. That key is included in the same keystore as the public key that is deployed on the FSC. You can also update sites that use symmetric keys to use asymmetric keys. To use asymmetric keys with Multi-Site Collaboration, all sites in the Multi-Site federation must use asymmetric keys. See Configure Multi-Site Collaboration to use asymmetric keys for details.