License acquisition error codes
If the DRM Cloud service can't produce a license response, the error is indicated by an HTTP status code in the 4xx or 5xx range. The body of the response contains a JSON object with more details about the error, for example:
{
"code": "drm_3032",
"status": 403,
"message": "Token signature invalid",
"requestId": "c42e3599-3a47-4ed1-ad72-79a5b2a26b71"
}
| HTTP status | Code in JSON response | Description |
|---|---|---|
| 403 | drm_4002 | The payload of the license request is missing |
| 403 | drm_4003 | The payload of the license could not be parsed |
| 403 | drm_4005 | BrandGuid is invalid or configuration is missing |
| 403 | drm_3030 | The license was denied because the JWT token does not allow a license to be issued for this request (because of IP or KeyId restrictions) |
| 403 | drm_3031 | The JWT token or access_token is invalid or has expired |
| 403 | drm_3032 | The signature of the DRM token is invalid |
| 403 | drm_3033 | The KeyID in the DRM token could not be matched |
| 403 | drm_3034 | The IP address in the DRM token could not be matched |
| 403 | drm_3035 | Failed to decrypt the DRM token |
| 403 | drm_3036 | The UserToken is not valid |
| 403 | drm_3037 | The DRM token could not be properly validated |
| 403 | drm_3038 | The frontend signature validation failed |
| 403 | drm_3039 | The one-time token (nonce) has already been used |
| 403 | drm_3100 | License server error |
| 500 | common_3 | Internal server error |