This topic discusses how to troubleshoot MART server errors.
MART server rejects token from the management plane
Symptom
Failure to connect to the management plane.
Error message
The following message appears in the MART log:
ERROR REST - ExceptionMapper.toResponse() : Returning error response :
ErrorResponse{errorCode = hybrid.auth.HybridAuthTokenInvalid, errorMessage =
Runtime hybrid-authn-authz Service found token invalid}
Possible cause
This error can occur when the Kubernetes cluster time is not in sync with network
time protocol (NTP). This
situation can result in a valid token from the management plane being rejected as invalid.
Resolution
Sync the cluster time with NTP. This problem can occur regardless of whether
you are using the MART ingress or Apigee Connect.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-10 UTC."],[[["Version 1.2 of the Apigee hybrid documentation is end of life, and users should upgrade to a newer version."],["MART server connection failures to the management plane can occur, resulting in an \"invalid token\" error in the MART log."],["The root cause of the \"invalid token\" error may be a Kubernetes cluster time that is out of sync with the network time protocol (NTP)."],["To resolve the MART server \"invalid token\" error, ensure the Kubernetes cluster time is synchronized with NTP, regardless of whether MART ingress or Apigee Connect is in use."]]],[]]
