Skip to main content
The SDK logs token acquisition, cache hits and refresh activity through mudraid.machine_auth. Configure a handler and level in your application:
The SDK reads process environment variables explicitly. A missing configuration error should be checked against the selected prefix; a token refusal should be checked against the exact client, environment, assertion audience, resource and approved scopes. SDK tests check that access tokens and client assertions are not written to SDK logs. Application logs, custom signers and HTTP wire logging remain separate: do not record private keys, authorization headers or token-response bodies. Client identifiers may appear in diagnostic messages. For a protected-resource failure, record the status and a safe correlation ID, then inspect that resource’s validation/enforcement evidence. A successful token exchange alone does not establish that the resource integration is correct. See Handle errors.