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"]],[["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-04-01 UTC."],[[["This page details the `HmacKeyMetadata` class for Google Cloud Storage, which is used to manage HMAC keys for service account authentication."],["HMAC keys provide a method for applications to authenticate with Google Cloud Storage and are associated with service accounts, which determine the authorization of requests."],["The document provides a history of the `HmacKeyMetadata` class with different version links ranging from version 2.11.0 all the way to 2.37.0-rc."],["The `HmacKeyMetadata` class has testing modifiers to change attributes like `access_id`, `id`, `kind`, `project_id`, `service_account_email`, `time_created`, `updated`, and `etag` for testing purposes."],["The `HmacKeyMetadata` class also has functions to get information from the storage like the `access_id`, `id`, `kind`, `project_id`, `service_account_email`, `state`, `time_created`, and `updated`, as well as static functions for setting the `state_active`, `state_inactive`, and `state_deleted`."]]],[]]