Description
You can encrypt your configuration and properties files using the GenRocket Runtime encrypt file command. Once a file has been encrypted, it will end with .gref (.gref => GenRocket Encrypted File). Only the GenRocket Runtime can decrypt files you've encrypted with this command. When the GenRocket Runtime reads a file ending in .gref it will automatically unencrypt the file once loaded in the computer's memory.
Command
-ef <rawFile> --encrypt-file <rawFile>
Required Parameters
- <rawFile> - the location and name of the file to be encrypted
How to Encrypt Your Configuration File
- Open your terminal application or a command window.
- Navigate to the directory where your configuration file is located.
- Note: You can also enter the full path as part of the command.
- Use the genrocket -ef command with the file name or enter the complete path.
- You will now have a copy of your encrypted config file with the extension .gref.
- You can now delete or move your unencrypted config file to a secure location.
Update File Name Where Applicable
You must update the file name anywhere it is being used by GenRocket because .gref is added to the end of the file name as the extension. Some examples include:
- Organization Resources (if file name specifically included in value)
- Generator Parameters
- Receiver Parameters
- GenRocket Features (e.g., G-Migration+, G-Delta, etc.)