Client Status Codes: CPIX
The below table provides the status codes and their descriptions, expected UI behavior (if applicable), and comments to include if you report the error to Verimatrix Customer Care.
MDRM Error Code | Message | Description | HTTP Error Code |
|---|---|---|---|
MDRM-900 | An unexpected error occurred while processing the request | Generic error | 500 |
MDRM-901 | Authorization token is required | This error is seen when the Authorization token itself is missing in the header of the Content encryption Request. | 401 |
MDRM-902 | Failed to decode JSON web token; malformed | This error is seen when the Authorization token in the header of the get License request is incorrect. | 401 |
MDRM-903 | Content ID must be present in the request | This error is seen when the content Id in the request body of the content-encryption request is missing. | 400 |
MDRM-904 | Content ID must match ID in the request | This error is seen when the content Id and the Id present in the request body of the content-encryption request does not match. | 400 |
MDRM-905 | Subject claim does not refer to the requested content ID | This error is seen when the sub claim present in the payload of the JWT token sent via the header of the Content encryption Request does not match with the contentId present in the request body. | 400 |
MDRM-906 | Requested content encryption key does not exist | 500 | |
MDRM-907 | An error occurred while retrieving encryption key from backend service | 500 | |
MDRM-908 | Key ID could not be parsed into a valid UUID | This error is seen when the keyId claim present in the header of the JWT token sent via the header of the License request value is not in UUID format. | 400 |
MDRM-909 | Failed to serialize response into XML | 500 | |
MDRM-910 | Failed to transform request to XML | The CPIX request cannot be transformed to XML. This is due to a missing or malformed CPIX document in the request. | 400 |
MDRM-911 | No public key defined, and key encryption turned on | 500 | |
MDRM-912 | Malformed request, missing or invalid parameter | The kid, issuer, or subject is not in the query parameters while sending request to CPIX using a signed CPIX document in the request body. | 400 |
MDRM-913 | Failed to import key for validating CPIX Doc Signature | The key import for validating the CPIX Doc signature failed. | 500 |
MDRM-914 | CPIX document has no signatures | The CPIX signed doc path received a request with no signature in the request body. | 401 |
MDRM-915 | CPIX document has no overall signature | The signed document has no whole document signature. | 401 |
MDRM-916 | CPIX document signature invalid | The signature in the CPIX document is not valid. | 401 |
MDRM-917 | Exception while verifying CPIX document signature | The signature in the CPIX document can not be verified. | 401 |
MDRM-918 | Signature does not use required algorithms | The signature violates one of the following:
Transforms allowed are:
For two Transforms, the transforms must be in the order: http://www.w3.org/2000/09/xmldsig#enveloped-signature http://www.w3.org/TR/2001/REC-xml-c14n-20010315 | 401 |
MDRM-919 | Certificate in the signed CPIX document is invalid | 401 | |
MDRM-920 | CPIX document has an invalid or missing DeliveryDataList | The CPIX request body is missing or has an invalid DeliveryDataList block. | 401 |
MDRM-921 | CPIX document has no DeliveryKey within the DeliveryDataList | The CPIX request body has a DeliveryDataList block, but the DeliverKey is missing. | 401 |
MDRM-922 | CPIX document signing key is invalid | The document signing key does not align with the service access key signaled in the request. | 401 |
MDRM-923 | Mismatching SPEKE and CPIX versions | SPEKE v2 is only compatible with CPIX v2.3. | 401 |
MDRM-924 | ContentKeyList or ContentKey not present in request | ContentKey or ContentKeyList are not present in the request body. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-925 | ContentKeyUsageRuleList or ContentKeyUsageRule not present in request | ContentKeyUsageRule or ContentKeyUsageRuleList are not present in the request body. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-926 | DRMSystem or DRMSystemList not present in request | DRMSystem or the DRMSystemList are not present in the request body when making requests to the CPIX v2.3 service endpoint using SPEKE v2. | 400 |
MDRM-927 | AudioFilter and VideoFilter not present in request in one or more ContentKeyUsageRule | If both AudioFilter and VideoFilter are missing inside a ContentKeyUsageRule, the request fails. If only one of them is present the request passes. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-928 | IntendedTrackType not present in request | The IntendedTrackType attribute is not present in a ContentKeyUsageRule element. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-929 | ContentKey@commonEncryptionScheme non compatible with DRMSystem id | The request for a Fairplay SystemId uses ‘cenc’ as the commonEncryptionSchema. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-930 | Invalid combination of IntendedTrackTypes | If an IntendedTrackType is set to ALL, then all track types must be ALL. | 400 |
MDRM-931 | Wrong version in request | The body’s request includes a CPIX version that is not v2.3. Applies when making requests to the CPIX v2.3 service using SPEKE v2. | 400 |
MDRM-932 | A timeout occurred while retrieving encryption key from backend service | There was a timeout while contacting the key manager to retrieve a key. The response contains the retry-after header with a randomized retry interval. | 503 |
MDRM-933 | Invalid DRM System Id | The body’s request contains an invalid DRM system ID. The only valid DRMs are Widevine, PlayReady, and FairPlay. | 400 |
MDRM-934 | Too many requests | The service is overloaded and the request is rejected as part of load shedding | 503 |
MDRM-935 | An invalid Key ID or Subject was encountered in license request | An invalid keyId or subject was encountered in the license request that prevented the key manager from retrieving the encryption key. | 400 |
Updated 2 months ago