Keyfactor Command can use a file to pass the configuration information into the configuration wizard, which saves a significant amount of typing when you do your initial installation. You may have been provided one of these already configured for your initial implementation, or you may have created one after typing in all the configuration information during the initial implementation. If you can locate this file, it can save some time in the upgrade process. You won't want to import the existing file again, as the file structure may change between versions and importing the file again will overwrite any changes you might have made to the configuration since your initial install, but you can refer to the file for previous configuration information.
The configuration files generally have a .cmscfg extension. When creating the file, you have the option to encrypt and password protect the file. If the file has been password protected, sensitive information in the file, such as any service account passwords, will be encrypted, but the remainder of the file will be human readable. You will need to know the password used to protect the file in order to use the file in its complete state.
Configuration files created for Windows installations under IIS cannot be used with container installations under Kubernetes, but you can refer to the files for reference when building your values.yaml file.
Was this page helpful? Provide Feedback