TeamcenterKnowledge

System Administration > File Management System > Administering FMS > Configuring FMS > Configuring FMS ticket signing keys > Configuring FMS to use public-private (asymmetric) key pairs

Renew the public keys in the asymmetric keystore

You can renew your public keys manually or by using Deployment Center. Use Deployment Center to renew the public key Use the following steps to use Deployment Center to renew the public key in the keystore. Procedure Open Deployment Center, go to the Components tab, and select the FSC Keys component. Ensure Generate New Keys is selected under General Settings. Ensure Use Asymmetric Keys (advanced) is selected under FSC Key Options. Enter and confirm the password of the existing keystore (.p12) file containing the public key and the admin key for this site. When you generate and run the Deployment Center installation scripts on the servers, the key pair and keystore file are updated with the new public key. The keystore file is also updated with a new administrative symmetric key. Manually renew the public key Perform the following steps from a Teamcenter command prompt to manually renew your public key. Commands requiring credentials must be run by a Teamcenter administrator with DBA privileges. Procedure Use the install_fms_keys utility to generate a new private key in the Teamcenter database as follows: Copy install_fms_keys -u=Tc-admin-user -p=password -g=group -f=install -overwrite The private key is added to the Teamcenter database. Use the install_fms_keys utility to export the public key corresponding to the private key in the Teamcenter database as follows: Copy install_fms_keys -u=Tc-admin-user -p=password -g=group -f=exp_pubkey -file_password=key_pass Where key_pass is the password for the exported keystore file. The public key is saved as a new .p12 keystore file. Use the keygen.bat utility (keygen.sh on Linux) to add the new public key to the previously existing keystore (FMSPublicKeys.p12) overwriting the current public key in the keystore as follows: Copy keygen -importpubkey -keystore p12_keystore_file -storepass key_pass -srckeystore src_key_file -srcstorepass src_key_pass -overwrite Where: p12_keystore_file The file name of the .p12 file holding the public key being replaced (FMSPublicKeys.p12). key_pass The password for the .p12 file holding the public key being replaced (FMSPublicKeys.p12). 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. (Optional.) You can regenerate and import the administrative symmetric key into the .p12 keystore file using the -overwrite option of the keygen utility. Doing so replaces the existing administrative key with a new key. For example: Copy keygen -genadminkey -keystore p12_keystore_file -storepass key_pass -overwrite Where: p12_keystore_file The file name of the .p12 file holding the public key. key_pass The password of the .p12 file holding the public key. Deploy the new .p12 keystore file to each of the FSCs.

Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/uuc1737238583853/fhe1737238587390/nxs1737238591363/xnr1737238592312/vhw1737238592403/xid2238417.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)