System Administration > File Management System > Administering FMS > Configuring FMS > Configuring FMS ticket signing keys > Configuring FMS to use public-private (asymmetric) key pairs
Convert sites that use symmetric keys to use asymmetric keys
You can update an existing FMS deployment that uses symmetric keys to one that uses asymmetric keys. Perform the following tasks to update an existing FMS deployment: Prepare for the update. Set the Teamcenter preference to specify using asymmetric keys. Generate a new public-private key pair in the Teamcenter deployment. Export the public key from Teamcenter to a keystore file. Generate and add the symmetric key to the asymmetric keystore. Deploy the keystore file on the FSC and update the FSC configuration. Restart all processes. Run all commands from a Teamcenter command prompt. Commands requiring credentials must be run by a Teamcenter administrator with DBA privileges. Prepare for the update Shut down the FSCs, Pool Manager, and all TcServer processes using the Teamcenter Management Console. Set the Teamcenter preference to specify using asymmetric keys Use the preferences_manager utility to set the FMS_USE_ASYMMETRIC_KEYS preference as follows: Copy preferences_manager -u=Tc-admin-user -p=password -g=group -mode=import -scope=SITE -action=OVERRIDE -preference=FMS_USE_ASYMMETRIC_KEYS -values="true" Generate a new public-private key pair in the Teamcenter deployment Run 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 The key is created and installed in the Teamcenter database. Export the public key from Teamcenter to a keystore file Once the private key is generated and updated in the database, use the install_fms_keys utility to export the public key corresponding to the private key 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 exported from the Teamcenter database and saved in the current directory as a keystore file named FMSPublicKeys.p12. Generate and add the symmetric key to the asymmetric keystore With asymmetric keys configured for ticket validation for file operations, FMS still uses a symmetric key for administrative commands. Use the keygen.bat utility (keygen.sh on Linux) to add this symmetric key to the keystore (.p12 file) that holds the public key for file operations: Copy keygen -genadminkey -keystore p12_keystore_file -storepass key_pass Where: p12_keystore_file The file name of the .p12 file holding the public key (FMSPublicKeys.p12). key_pass The password of the .p12 file holding the public key (FMSPublicKeys.p12). The administrative key is generated and added to the FMSPublicKeys.p12 keystore. Deploy the keystore file on the FSC and update the FSC configuration Use the following steps to update the FSC to use asymmetric keys and the new keystore file: Procedure Copy the .p12 keystore file to the FSC_Home directory. Update the FMS primary configuration file (FSC_HOME\fmsmaster_fscid.xml) to specify using asymmetric keys by adding a ticketkeys element. For example: Copy
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/uuc1737238583853/fhe1737238587390/nxs1737238591363/xnr1737238592312/vhw1737238592403/xid2238415.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)