Receiver file signing (Beta)
CFT provides a file signing feature to sign outgoing files, letting receivers verify authenticity and integrity. Signing keys are created and managed by Tenant Managers in the Admin Portal.
Quick reference
- CFT supports file signing for PGP only (OpenPGP RFC 4880 compliant).
- Receiver Encryption is required to be enabled on the same workflow.
- Both Armored and Binary PGP keys are supported.
- Only Tenant Managers can create and manage PGP keys.
Understanding the signing flow
When file signing is enabled, the file must be decrypted successfully first before it can be verified.
Sender → CFT scans file → CFT signs file → CFT encrypts file → Receiver
The status of the transfer at each stage can be monitored in the Admin Portal logs.
Prerequisites
To enable this feature, you must create two keys in the CFT Admin Portal:
Receiver Key: Used for file encryption.
Receiver File Signing Key: Used for file signing. Only PGP type is supported for now.
For more information, refer to Understanding key types.
Set up file signing
Follow these steps to configure file signing in your transfer workflow.
| Step | Task | Environment | Notes |
|---|---|---|---|
| 1 | Create a Receiver key | CFT Admin Portal | Required for encryption. |
| 2 | Create a Receiver File Signing key | CFT Admin Portal | Key type should be PGP. |
| 3 | Enable Receiver file signing + receiver file encryption | CFT Admin Portal | Configure within your Workflow. |
| Optional | Enable file signing webhook | CFT Admin Portal | This is optional. Refer to Webhooks section. |
Troubleshooting
Refer to the Troubleshooting guide for a list of common errors and resolutions.
