Many of the KBC components use the Encryption API; it encrypts sensitive values which are supposed to be securely stored and decrypted inside the component itself.
This means that the encrypted values are available inside the components and are not accessible to the API users. Also, there is no decryption API and there is no way the end-user can decrypt the encrypted values.
Decryption is only executed when serializing configuration to the configuration file for the Docker container. The decrypted data are stored on the Docker host drive and are deleted immediately after the container finishes. The actual component code always reads the decrypted data.
When saving arbitrary configuration data, values marked by the
# character are automatically encrypted.
Given the following configuration:
After you save the configuration, you will receive:
Once the configuration has been saved, the value is encrypted and there is no way to decrypt it. What values are encrypted is defined by the component. It means you cannot freely encrypt any value unless the component explicitly supports it.
For example, if the component states that it requires the configuration
it means the password will always be encrypted and the username will not be encrypted. You
#username because the component does not expect such a key to exist
(although its value will be encrypted and decrypted normally). Internally, the
encrypt API call is used to encrypt the values before saving them.
The UI prefers encrypted values to plain values; if you provide both
#password, only the latter will be saved.
The following configuration
The Encryption API can encrypt
either strings or arbitrary JSON data. For strings, the whole string is encrypted. For JSON data,
only the keys which start with the
# character and are scalar are encrypted. For example, encrypting
If you want to encrypt a single string, a password for instance, the body of the request is simply the text string you want to encrypt (no JSON or quotation is used). To give an example, encrypting
Content-Type header is used to distinguish between treating the body as a string (
text/plain) or JSON (
You can use the Console in Apiary to call the API resource endpoint.
componentId(required) — id of a KBC component
projectId(optional) — id of a KBC project
configId(optional) — id of a component configuration
Depending on the provided parameters, different types of ciphers are created:
If only the component id is provided, then the cipher starts with
KBC::ComponentSecure:: and it can be
decrypted in all configurations of the given component.
If both the component id and project id are provided, then the cipher starts with
KBC::ProjectSecure:: and it
can be decrypted in all configurations of the given component within the given project.
If all three (component id, project id and configuration id) are provided, then the cipher starts with
KBC::ConfigSecure:: and it can be decrypted only within the given configuration of the given component in the given project.
The following rules apply to all ciphers:
By default, values encrypted in component configurations are encrypted using the
This means that the cipher is not transferable between stacks, components or projects. It is transferable
between different configurations of the same component within the project where it was created. If, for some
reason, you create a configuration containing
KBC::ConfigSecure:: ciphers, note that the configuration will not work when copied.