Represents the metadata for a Google Cloud Storage HmacKeyResource.
HMAC keys allow applications to authenticate with Google Cloud Storage using HMAC authentication. Applications can create a limited number of HMAC keys associated with a service account. The application can use the HMAC keys to authenticate with GCS. GCS will use the service account permissions to determine if the request is authorized.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This webpage details the `HmacKeyMetadata` class, which is used to represent the metadata for a Google Cloud Storage HMAC key resource, which allows applications to authenticate with Google Cloud Storage using HMAC authentication."],["The latest version of this documentation is for version 2.37.0-rc, and it provides access to the documentation for all versions going back to 2.11.0."],["The `HmacKeyMetadata` class provides methods to set and retrieve various attributes, including `access_id`, `id`, `kind`, `project_id`, `service_account_email`, `time_created`, `updated`, `state`, and `etag`, with testing modifiers that are used in tests for mocking."],["HMAC keys are tied to a service account and can be used by applications to authenticate with GCS, with GCS then determining if the request is authorized based on service account permissions."],["The class also provides static methods for the states: `state_active`, `state_inactive`, and `state_deleted`."]]],[]]
