Properties Inspector
Load property files across environments, configure decryption per env, and compare values side by side.
{env} as placeholder. Regex allowed, e.g. config-(?<env>\w+)\.ya?ml.
How it works
This tool mirrors the two methods of the MuleSoft
secure-properties-tool.jar:
- String — encrypt or decrypt a single value, the same output you'd wrap in
![...]inside a property file. - File — process a
.propertiesor.yamlfile, encrypting or decrypting every value at once.
Keys are read as raw UTF-8 bytes, PKCS5/PKCS7 padding is applied, and output is Base64 encoded. The IV is either derived from the key or randomly generated and prepended to the ciphertext.
Wrap the value in your Mule property file as
![encryptedValue] so the Secure Configuration Properties
module decrypts it at runtime.
Everything runs locally in your browser. No values are sent anywhere.
How it works
Compare property files across environments side by side and spot drift before it becomes an incident:
- Load — drop files or a folder. Environments are detected from the filename with a
{env}pattern (e.g.{env}-configuration.yaml). - Secure files — a second pattern flags encrypted configs. Provide a per-env key, algorithm, mode, and IV option to decrypt them.
- Compare — every key shows up in a single row with one column per env. Missing values are highlighted red, differing values yellow, and cells with no key stay encrypted in blue.
Click any cell or key to see the full value in a popup, with a copy button. Toggle fullscreen for a clearer table, or mask and reveal decrypted secrets one cell at a time.
Supports nested YAML maps, block sequences, and the
.properties format. Encrypted list items are decrypted
per element.
Everything runs locally in your browser. Files and keys never leave your machine.