Enabling Project Managed Encryption
(introduced: version 0.6)
Project Managed Encryption can be enabled via the API. To do this, POST with the passphrase and optionally a reminder hint about the passphrase. If managed encryption is already enabled, a 409 error response will be returned.
Enabling managed encryption will modify all unencrypted forms in the project, and as a result the version of all forms within the project will also be modified. It is therefore best to enable managed encryption before devices are in the field. Any forms in the project that already have self-supplied encryption keys will be left alone.
Path parameters
The numeric ID of the Project
Response
OK
Changes
Changed in 3 of the 54 revisions of this API.4
- ○
api operation id
Enabling Project Managed Encryptionremoved and replaced withenableProjectManagedEncryptionapi-operation-id-removed
- ○
- ○
removed the non-success response with the status
403response-non-success-status-removed
- ○
- ○
api operation id
enableProjectManagedEncryptionremoved and replaced withEnabling Project Managed Encryptionapi-operation-id-removed
- ○
added the non-success response with the status
403response-non-success-status-added
This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○