License acquisition error codes

If DRM Cloud service is not able to produce license response, the error is signaled as 4xx or 5xx response HTTP Status. The body of the response containd JSON 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 JWT token does not allow to issue a license for this request (because of IP or KeyId restrictions)
403	drm_3031	JWT token or access_token is not valid or it has expired.
403	drm_3032	Signature of DRM token is invalid
403	drm_3033	KeyID in DRM token could not be matched
403	drm_3034	IP in DRM token could not be matched
403	drm_3035	DRM token decryption failed
403	drm_3036	UserToken not valid
403	drm_3037	DRM token could not be validated correctly
403	drm_3038	Frontend signature validation failed
403	drm_3039	One-time token (nonce) has been already used
403	drm_3100	License server error
500	common_3	Internal server error