| Previous | Next |
| TPM_20_E_TOO_MANY_CONTEXTS | TPM_20_E_REBOOT |
TPM_20_E_AUTH_UNAVAILABLE
This status means that the selected entity cannot supply the authorization material or authorization mode required by the command. It is not a statement that a password is merely unknown. For an object, authorization requires the relevant public and sensitive portions to be available to the TPM; for an NV index, the requested read or write authorization must be enabled by its attributes.
Typical causes
- An application attempts to authorize an external or incomplete object representation that lacks the necessary sensitive state.
- An NV index is read or written using a policy or HMAC/password path that its
TPMA_NV_POLICYREAD,TPMA_NV_POLICYWRITE,TPMA_NV_AUTHREADorTPMA_NV_AUTHWRITEattributes do not permit. - A cached handle refers to an entity with different attributes after reprovisioning, context reload or deployment to another TPM.
Do not treat it as a bad secret
Changing the authorization value will not make an unavailable authorization mode valid. Inspect the command role, entity type, object loading state and raw public or NV attributes. For NV storage, determine separately whether the operation is a read, write or policy-secret flow.
TCG: authorization availability and NV attributes · TPM 2.0 Library · tpm2-tools authorization formats
Looking for a different code? Search another status or error code.