multi-router.aidocs

Machine Identity

TroubleshootingEnterprise

Machine identity authentication errors, with their causes and fixes.

A machine request that fails authentication returns 401, or 503 when signing keys or bindings are briefly unavailable. On the OpenAI-format endpoints, such as Chat Completions, Models and Responses, a 401 has the type authentication_error and code invalid_machine_token, and a 503 has the type server_error and code machine_identity_unavailable. Messages and the Claude Proxy endpoints use their own error format with the same message.

Errors

Each message points to one part of the setup:

MessageCause and fix
invalid or missing machine credentialThe token is malformed, or its audience matches no issuer. Request the token for the issuer's token audience.
machine identity issuer is disabledThe issuer is turned off. Enable it.
machine token issuer does not match the registered issuerThe token's iss differs from the Issuer URL. Check for a trailing path or a different cluster.
machine token uses an unsupported signing algorithmThe platform signs with an algorithm outside the supported list.
machine token has no usable key identifierThe token has no kid header. Use a platform that sets it.
machine issuer does not recognize the token signing keyThe token's key is missing from the issuer's published keys.
machine issuer signing keys are temporarily unavailableThe issuer cannot be reached and Reject requests is set, or cached keys expired. Check the issuer card.
machine token signature is invalidThe signature fails verification, or the signing key's type differs from the token's algorithm.
machine token is expired or outside its valid time windowThe token expired, or the workload's clock is more than 60 seconds ahead. Read or request a fresh token for each request.
machine token exceeds the issuer lifetime limitThe token is valid for longer than the issuer's Maximum token lifetime. Shorten the token or raise the limit.
machine token has no caller binding for this subjectNo enabled binding matches the token's subject. Check the subject in the binding.
machine caller binding is disabledThe binding chosen for the subject is turned off. Enable it.
machine identity authority is temporarily unavailableMulti-Router could not read bindings just now. Retry.
machine identity is not permitted to use this endpointStatus 403, code insufficient_scope. The endpoint needs a scope the binding lacks, such as List available models, or is a management endpoint.
the requested model or router was not foundThe request names a router outside the binding, names no router when the binding has several, or names a model with no router.

Finding the subject and audience

Decoding a token shows its claims. The token's middle part is base64url-encoded JSON, which this Python line prints:

Print a token's claimsbash
python3 -c 'import sys,base64,json; p=open(sys.argv[1]).read().split(".")[1]; print(json.dumps(json.loads(base64.urlsafe_b64decode(p+"="*(-len(p)%4))),indent=2))' token

Compare its iss, sub, aud and expiry with the issuer's URL and token audience and the binding's subject.

Calling Multi-RouterOverview
Was this helpful?