Client Status Codes: FairPlay
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 | Failed to decrypt payload | The request body in the get license request is incorrect. | MDRM-1006 |
400 | SPC must be present in request | The SPC in the request body is missing. | MDRM-1004 |
400 | Failed to parse request payload | MDRM-1007 | |
400 | Failed to extract SK..R1 from request payload | MDRM-1008 | |
401 | Authorization token is required | The Authorization token itself is missing in the header of the License Request. | MDRM-1001 |
401 | Failed to decode JSON web token; malformed | The Authorization token in the header of the get License request is incorrect. | MDRM-1002 |
404 | Failed to resolve encryption key for organization | MDRM-1003 | |
404 | Requested content encryption key does not exist | This error is seen when MDRM-806 is returned from VKM. No content key was found for the requested content. | MDRM-1011 |
500 | An unexpected error occurred while processing the request | Generic error | MDRM-1000 |
404 | An error occurred while retrieving FairPlay DRM information from the database | The get License request is sent without FairPlay DRM being provisioned for that specific org Id. | MDRM-1005 |
500 | An error occurred while retrieving encryption key from backend service | MDRM-1009 | |
500 | Failed to encrypt content key | MDRM-1010 |
Updated over 1 year ago
What’s Next