Specify the sequence of delegates used to sign a blob.
With this option the application can sign a URL even if the account associated with the current credentials does not have direct roles/iam.serviceAccountTokenCreator on the target service account.
[[["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-03-14 UTC."],[[["The latest version available is 2.37.0-rc, which can be accessed via a specific link."],["The provided content lists multiple versions of `SigningAccountDelegates`, ranging from 2.11.0 to 2.37.0-rc."],["`SigningAccountDelegates` is used to specify the sequence of delegates required to sign a blob, even if the associated account lacks direct token creator roles."],["The `SigningAccountDelegates` class contains a function called `name()` that returns a character string."],["The list of versions available begins with version 2.20.0, and they all contain a class called `SigningAccountDelegates` that allows the specification of delegates used to sign a blob."]]],[]]
