CreateAuthorizerRequest

import type { CreateAuthorizerRequest } from "https://aws-api.deno.dev/v0.3/services/iot.ts?docs=full";

interface CreateAuthorizerRequest {

authorizerFunctionArn: string;

authorizerName: string;

enableCachingForHttp?: boolean | null;

signingDisabled?: boolean | null;

status?: AuthorizerStatus | null;

tags?: Tag[] | null;

tokenKeyName?: string | null;

tokenSigningPublicKeys?: {

[key: string]: string | null | undefined;

} | null;

}

§Properties

authorizerFunctionArn: string

[src]

The ARN of the authorizer's Lambda function.

authorizerName: string

[src]

The authorizer name.

enableCachingForHttp?: boolean | null

[src]

When true, the result from the authorizer’s Lambda function is cached for clients that use persistent HTTP connections. The results are cached for the time specified by the Lambda function in refreshAfterInSeconds. This value does not affect authorization of clients that use MQTT connections.

The default value is false.

signingDisabled?: boolean | null

[src]

Specifies whether IoT validates the token signature in an authorization request.

status?: AuthorizerStatus | null

[src]

The status of the create authorizer request.

tags?: Tag[] | null

[src]

Metadata which can be used to manage the custom authorizer.

Note: For URI Request parameters use format: ...key1=value1&key2=value2... For the CLI command-line parameter use format: &&tags "key1=value1&key2=value2..." For the cli-input-json file use format: "tags": "key1=value1&key2=value2..."

tokenKeyName?: string | null

[src]

The name of the token key used to extract the token from the HTTP headers.

tokenSigningPublicKeys?: {

[key: string]: string | null | undefined;

} | null

[src]

The public keys used to verify the digital signature returned by your custom authentication service.