General Information
Policy Type
UI Documentation
📖 For detailed information: [UI Documentation Link - Link will be added here]
Description
Decryption policy decrypts encrypted data using cryptographic keys. It reads encrypted data from source variables, decrypts them using specified cipher algorithms, and stores the decrypted data in target variables. This policy provides data confidentiality capabilities by reversing encryption operations. ⚠️ Implementation Status: This policy is currently not implemented in Management API. This policy cannot be created or managed through the Management API at this time. This documentation is provided for reference purposes and will be updated when full API support is added in a future release.Endpoints
List Policies
Add Policy
Update Policy
Delete Policy
List Policies
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
Response
Success Response (200 OK)
Add Policy
Endpoint
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer {token} | Yes |
| Content-Type | application/json | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name (unique identifier) |
Request Body
Note: The current DTO implementation is empty. The following JSON structure is based on the underlyingPolicyDecryption and PolicyDecryptionDef classes and represents the expected structure when full API support is added.
Full JSON Body Example - Basic Decryption
Full JSON Body Example - Dynamic Cipher Algorithm
Full JSON Body Example - Multiple Decryption Definitions
Request Body Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| type | string | Yes | - | Must be "policy-decryption" |
| description | string | No | - | Policy description |
| active | boolean | No | true | Whether the policy is active |
| policyCondition | object | No | null | Policy condition |
| errorMessageList | array | No | [] | List of error messages |
| operationMetadata | object | Yes | - | Operation metadata |
| policyDecryptionDefList | array | Yes | - | List of decryption definitions |
Decryption Definition (policyDecryptionDefList)
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| id | string | No | - | Definition ID |
| description | string | No | - | Definition description |
| sourceVar | object | Yes | - | Source variable containing encrypted data |
| targetVar | object | Yes | - | Target variable for decrypted data |
| cipherAlgorithm | string | No | null | Cipher algorithm (if static) |
| cipherAlgorithmVar | object | No | null | Variable containing cipher algorithm name (if dynamic) |
| cryptoKeyInfoId | string | No | null | Crypto key info ID (for symmetric algorithms or asymmetric with KEY type) |
| certificateId | string | No | null | Certificate ID (for asymmetric algorithms with CERTIFICATE type) |
| enumKeyCertificateType | string | No | KEY | Key/certificate type |
| ivExists | boolean | No | false | Whether initialization vector (IV) exists |
| ivVar | object | No | null | Variable containing IV (if ivExists=true) |
| ivEncodingType | string | No | null | IV encoding type (if ivExists=true) |
| inputEncodingType | string | Yes | - | Input encoding type of encrypted data |
EnumCipherAlgorithm (cipherAlgorithm)
Symmetric Algorithms:AES_CBC_NoPadding- AES/CBC/NoPaddingAES_CBC_PKCS5Padding- AES/CBC/PKCS5Padding (requires IV)AES_ECB_NoPadding- AES/ECB/NoPaddingAES_ECB_PKCS5Padding- AES/ECB/PKCS5PaddingDES_CBC_NoPadding- DES/CBC/NoPaddingDES_CBC_PKCS5Padding- DES/CBC/PKCS5Padding (requires IV)DES_ECB_NoPadding- DES/ECB/NoPaddingDES_ECB_PKCS5Padding- DES/ECB/PKCS5PaddingDESede_CBC_NoPadding- DESede/CBC/NoPaddingDESede_CBC_PKCS5Padding- DESede/CBC/PKCS5Padding (requires IV)DESede_ECB_NoPadding- DESede/ECB/NoPaddingDESede_ECB_PKCS5Padding- DESede/ECB/PKCS5Padding
RSA_ECB_PKCS1Padding- RSA/ECB/PKCS1PaddingRSA_ECB_OAEPWithSHA_1AndMGF1Padding- RSA/ECB/OAEPWithSHA-1AndMGF1PaddingRSA_ECB_OAEPWithSHA_256AndMGF1Padding- RSA/ECB/OAEPWithSHA-256AndMGF1Padding
EnumEncodingType (inputEncodingType, ivEncodingType)
BASE64- Base64 encodingHEXADECIMAL- Hexadecimal encoding
EnumKeyCertificateType (enumKeyCertificateType)
KEY- Use cryptographic key (from cryptoKeyInfoId)CERTIFICATE- Use certificate (from certificateId)
Variable Object (sourceVar, targetVar, ivVar, cipherAlgorithmVar)
| Field | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Variable name |
| type | string | Yes | Variable type |
| headerName | string | No* | Header name (required if type=HEADER) |
| paramName | string | No* | Parameter name (required if type=PARAMETER) |
| jsonPathValue | string | No* | JsonPath expression (required if type=BODY for JSON) |
| xpathValue | string | No* | XPath expression (required if type=BODY for XML) |
| contextValue | string | No* | Context value (required if type=CONTEXT_VALUES) |
| dataType | string | Yes | Data type |
Variable Types
HEADER- Extract from HTTP headerPARAMETER- Extract from query/path/form parameterBODY- Extract from request/response body (XML, JSON, or raw)CONTEXT_VALUES- Extract from system context valuesCUSTOM- Extract using custom script
Response
Success Response (200 OK)
Error Response (400 Bad Request)
Update Policy
Endpoint
Request
Same as Add Policy. All fields can be updated.Response
Same as Add Policy.Delete Policy
Endpoint
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer {token} | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Response
Success Response (200 OK)
cURL Examples
Example 1: Add Basic Decryption Policy
Example 2: Update Decryption Policy
Example 3: Delete Decryption Policy
Notes and Warnings
-
⚠️ Implementation Status:
- This policy is currently NOT IMPLEMENTED in Management API
- Attempting to create or update this policy via Management API will fail
- This documentation is provided for reference purposes only
- Full API support will be added in a future release
-
Cipher Algorithm:
- Can be specified statically via
cipherAlgorithmor dynamically viacipherAlgorithmVar - If both are null, decryption will be skipped (data returned as-is)
- Algorithm must match the one used for encryption
- Can be specified statically via
-
Initialization Vector (IV):
- Required for CBC mode algorithms
- Set
ivExists: trueif IV is present - IV must be provided in
ivVarwith correctivEncodingType - IV encoding must match the encoding used during encryption
- ECB mode algorithms do not require IV
-
Input Encoding:
- Must match the output encoding used during encryption
BASE64- For Base64-encoded encrypted dataHEXADECIMAL- For hexadecimal-encoded encrypted data
-
Key/Certificate Management:
- Keys must be configured in Key Store before use
- Certificates must be configured in Certificate Store before use
- Use
enumKeyCertificateTypeto specify key or certificate source - Key/certificate must match the one used for encryption
-
Variable Types:
- Source and target variables can be from headers, parameters, body, or context
- Use appropriate variable types based on data location
- Encrypted data is typically stored in context or headers
-
Multiple Definitions:
- Multiple decryption definitions can be configured in one policy
- Each definition decrypts a different source variable
- Definitions are executed in order
-
Decryption Order:
- Decryption should be performed before other policies that need plaintext data
- Consider policy order when configuring decryption policies
-
Error Handling:
- Decryption failures will throw exceptions
- Configure error messages for better error handling
- Invalid keys or algorithms will cause decryption to fail
Permissions
User must haveAPI_MANAGEMENT + MANAGE permission in the project. For deployment operations (when deploy: true is set), user must also have API_MANAGEMENT + DEPLOY_UNDEPLOY permission.
Related Documentation
- List Policies - List all policies
- Add Policy - Add a policy
- Update Policy - Update a policy
- Delete Policy - Delete a policy
- Encryption Policy - Encrypt data

