AST Localization Error Codes (SubSystem 518)
Template Creation (Error Codes 10-19)
| Subsystem | Error Code | HTTP Code | Name | Comments |
|---|---|---|---|---|
| 518 | 10 | 409 | TemplateAlreadyExists | A template with the given key already exists |
Template Localization (Error Codes 20-29)
| Subsystem | Error Code | HTTP Code | Name | Comments |
|---|---|---|---|---|
| 518 | 20 | 406 | LanguageNotSatisfiable | None of the requested language ranges can be satisfied with the available locales |
Bad Request Codes (Error Codes 400 and 400x)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 400 | 400 | BadRequest | An unspecified Bad Request error. Look for details in the message. |
| 518 | 4001 | 400 | MissingField | A required field was missing in the request |
| 518 | 4002 | 400 | MalformedField | A field in the request had a wrong format |
| 518 | 4005 | 400 | MalformedBody | The request body was malformed and couldn't be parsed |
Unauthorized Codes (Error Codes 401 and 401x)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 401 | 401 | Unauthorized | There was a problem authorizing the request, see below for details |
Details about 518-401 Unauthorized
This error code includes cases like
- The header was missing
- The token could not be decoded
- The token is from a different realm than the tenant in the request path
- The token was expired (
exp), not yet valid (nbf) or issued in the future (iat) - The token's issuer (
iss) did not match the expected value discovered from the IdP- This is most likely a realm configuration problem in Keycloak, such as not configuring the "Frontend URL" setting
in the realm, which is required in a typical setup
- Failing to configure the Frontend URL will result in a mismatch between the issuer URL that was discovered by the service inside the cluster, and the issuer in the JWT issued for a client outside the cluster
- After changing the realm configuration, it is necessary to restart the service in order for it to rediscover the realm configuration
- This is most likely a realm configuration problem in Keycloak, such as not configuring the "Frontend URL" setting
in the realm, which is required in a typical setup
- The token's audience (
aud) didn't include all required values specified in the service config (default: none) - The token's signature did not match the public key discovered from the IdP
Forbidden / Bad Token Codes (Error Codes 403 and 403x)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 403 | 403 | Forbidden | The user has no permission to access the resource. The details of the failed authorization are printed in the logs |
Not Found Codes (Error Codes 404x)
| Subsystem | Error Code | HTTP Code | Name | Comments |
|---|---|---|---|---|
| 518 | 4041 | 404 | TemplateNotFound | A template with the given key does not exist |
OIDC Errors (Error Codes 100x)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 1000 | 500 | GeneralError | An unexpected error occurred while authenticating the request. See the log for details. |
| 518 | 1001 | 500 | IssuerNotConfigured | The OIDC issuer is not configured. This is probably due to misconfiguration of api.security.openidConnect.baseUrl. See the log for details. |
| 518 | 1002 | 404 | RealmDoesNotExist | The realm corresponding to the tenant ID in the request does not exist in the IDP. See the log for details. |
| 518 | 1003 | 503 | IdpUnavailable | The IDP could not be reached for OIDC discovery. This may be a temporary error or due to misconfiguration. See the log for details. |
| 518 | 1004 | 502 | BadResponse | The IDP response could not be parsed. See the log for details. |
| 518 | 1005 | 502 | UnexpectedError | The IDP returned an unexpected error response during OIDC Discovery. See the log for details. |
| 518 | 1006 | 500 | IssuerMismatch | The issuer URL returned from OIDC Discovery doesn't match the expected one generated from the configuration. This is probably due to realm misconfiguration in the IDP. See the log for details. |
| 518 | 1007 | 500 | UnsupportedFlow | The OIDC configuration returned from the IDP specified an unsupported flow. This probably due to realm misconfiguration in the IDP. See the log for details. |
General Error Codes (Internal Errors)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 500 | 500 | InternalError | An unexpected error occurred, check for details in the logs |
| 518 | 5001 | 500 | DbError | An unexpected error occurred during a database operation |
| 518 | 5002 | 500 | KafkaError | An unexpected error occurred during a Kafka operation |
| 518 | 503 | 503 | ServiceUnavailable | The service's availability was disrupted, look for details in the message. |
Configuration Errors (Error Codes 500xx)
| Subsystem | Error Code | HTTP Code | Name | Details |
|---|---|---|---|---|
| 518 | 50010 | 500 | UnknownTopicRoutingKey | An outbox item with an unknown topic routing key was encountered |
| 518 | 50020 | 500 | TrustStoreDoesNotExist | The trust store file does not exist |
| 510 | 50021 | 500 | TrustStoreRequired | A trust store was required for the configured SSL mode, but none was given |