Client Status Codes: Authorization
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 |
|---|---|---|---|
| 401 | Failed to decode JSON web token | The Authorization token in the header of the Content encryption request or get License request is incorrect. | MDRM-502 |
| 401 | Authorization token is required | The Authorization token itself is missing in the header of the Content encryption request or get License request. | MDRM-501 |
| 401 | Failed to resolve JSON web key | MDRM-504 | |
| 401 | JSON web token is invalid | MDRM-505 | |
| 401 | Failed to resolve session JSON web key | MDRM-506 | |
| 401 | JSON web token is expired | The exp claim present in the paylaod of the JWT token sent via the header of the License request value is expired. | MDRM-508 |
| 401 | JSON web token is missing issued at (iat) claim | The keyId claim present in the header of the JWT token sent via the header of the License request value is disabled. | MDRM-509 |
| 401 | JSON web token is inactive and may not be processed before the not before (iat) claim timestamp | The iat claim present in the payload of the JWT token sent via the header of the License request epoch value is at a later time. | MDRM-510 |
| 401 | JSON web token is inactive and may not be processed before the not before (nbf) claim timestamp | The nbf claim present in the payload of the JWT token sent via the header of the License request epoch value is at a later time. | MDRM-511 |
| 401 | Failed to retrieve signing key from the database | The keyId claim present in the header of the JWT token sent via the header of the License request value is already deleted. | MDRM-512 |
| 401 | Failed to decode JSON web token; malformed | MDRM-502 | |
| 401 | JSON web key is disabled | The keyId claim present in the header of the JWT token sent via the header of the License request value is already disabled. | MDRM-513 |
| 403 | Recipient does not allow access for specified audience | The aud claim present in the payload of the JWT token sent via the header of the License request value is incorrect. It is restricted to the scope during the creation/import of signing key. | MDRM-503 |
| 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 |
| 500 | An unexpected error occurred while processing the request | Generic error | MDRM-500 |
| 500 | Unable to sign session JSON web token | The encode JWT token with private key does not match with the public key present in the database. | MDRM-507 |
Updated over 1 year ago
What’s Next