class Aws::IoT::Types::CreateAuthorizerRequest


@return [Boolean]
authorization request.
Specifies whether AWS IoT validates the token signature in an
@!attribute [rw] signing_disabled
@return [Array<Types::Tag>]
</note>
“key1=value1&amp;key2=value2…”
For the cli-input-json file use format: “tags”:
“key1=value1&amp;key2=value2…”
For the CLI command-line parameter use format: &amp;&amp;tags
…key1=value1&amp;key2=value2…
<note markdown=“1”> For URI Request parameters use format:
Metadata which can be used to manage the custom authorizer.
@!attribute [rw] tags
@return [String]
The status of the create authorizer request.
@!attribute [rw] status
@return [Hash<String,String>]
your custom authentication service.
The public keys used to verify the digital signature returned by
@!attribute [rw] token_signing_public_keys
@return [String]
headers.
The name of the token key used to extract the token from the HTTP
@!attribute [rw] token_key_name
@return [String]
The ARN of the authorizer’s Lambda function.
@!attribute [rw] authorizer_function_arn
@return [String]
The authorizer name.
@!attribute [rw] authorizer_name
}
signing_disabled: false,
],
},
value: “TagValue”,
key: “TagKey”, # required
{
tags: [
status: “ACTIVE”, # accepts ACTIVE, INACTIVE
},
“KeyName” => “KeyValue”,
token_signing_public_keys: {
token_key_name: “TokenKeyName”,
authorizer_function_arn: “AuthorizerFunctionArn”, # required
authorizer_name: “AuthorizerName”, # required
{
data as a hash:
@note When making an API call, you may pass CreateAuthorizerRequest