Algorithm Not Permitted for Operation
URI: https://docs.ankatech.co/errors/algorithm-not-permitted-for-operation
HTTP Status: 422 Unprocessable Entity
When you see this
The key's algorithm is not permitted for the operation you requested under the active policy, even though the operation itself is well-formed.
Common Causes
- Requesting an operation with an algorithm the tenant policy disallows for that operation.
- Using an algorithm outside the permitted set for the requested action.
- A policy that restricts which algorithms may perform a given operation.
Response Example
{
"type": "https://docs.ankatech.co/errors/algorithm-not-permitted-for-operation",
"title": "Algorithm Not Permitted for Operation",
"status": 422,
"detail": "Algorithm 'RSA-2048' is not permitted for operation 'encrypt' under the active policy.",
"instance": "/api/v3/admin/keys/my-mlkem-key/operations",
"correlationId": "550e8400-e29b-41d4-a716-446655440000",
"timestamp": 1730000000
}
Content-Type: application/problem+json — the response follows RFC 7807 Problem Details.
How to Resolve
- Use a key whose algorithm is permitted for the operation under the tenant policy.
- Review the tenant's algorithm policy to see which algorithms are allowed for the operation.
- Request a policy change from a tenant administrator if the algorithm should be permitted, then re-submit.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.