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.

HTTP Error Code	Message	Description	MDRM Error Code
400	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.	MDRM-903
400	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.	MDRM-904
400	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.	MDRM-905
400	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.	MDRM-908
401	Authorization token is required	This error is seen when the Authorization token itself is missing in the header of the Content encryption Request.	MDRM-901
401	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.	MDRM-902
401	CPIX document has no signatures	The CPIX signed doc path received a request with no signature in the request body.	MDRM-914
401	CPIX document has no overall signature	The signed document has no whole document signature.	MDRM-915
401	CPIX document signature invalid	The signature in the CPIX document is not valid.	MDRM-916
401	Exception while verifying CPIX document signature	The signature in the CPIX document can not be verified.	MDRM-917
401	Signature does not use required algorithms	The signature violates one of the following: - Signature must specify only one SignatureMethod - Signature algorithm must be http://www.w3.org/2001/04/xmldsig-more#rsa-sha512 - Signature must only have one References tag - References tag must contain exactly one DigestMethod - Digest algorithm must be http://www.w3.org/2001/04/xmlenc#sha512 - Signature must have exactly one CanonicalizationMethod - Canonicalization algorithm must be http://www.w3.org/TR/2001/REC-xml-c14n-20010315 - Signature References must contain either one or two Transforms. Transforms allowed are: - http://www.w3.org/2000/09/xmldsig#enveloped-signature - http://www.w3.org/TR/2001/REC-xml-c14n-20010315 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	MDRM-918
400	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.	MDRM-912
401	Certificate in the signed CPIX document is invalid		MDRM-919
401	CPIX document has an invalid or missing DeliveryDataList	The CPIX request body is missing or has an invalid DeliveryDataList block.	MDRM-920
401	CPIX document has no DeliveryKey within the DeliveryDataList	The CPIX request body has a DeliveryDataList block, but the DeliverKey is missing.	MDRM-921
500	Failed to import key for validating CPIX Doc Signature	The key import for validating the CPIX Doc signature failed.	MDRM-913
500	An unexpected error occurred while processing the request	Generic error	MDRM-900
500	An error occurred while retrieving encryption key from backend service	MDRM-907
500	Failed to serialize response into XML		MDRM-909
400	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.	MDRM-910
500	Requested content encryption key does not exist		MDRM-906
500	No public key defined, and key encryption turned on		MDRM-911