Experimental
@aws-cdk/aws-bedrock-agentcore-alpha is an experimental (alpha) package: its API may change in any release, without a major version bump.
CustomJwtConfiguration Struct
Custom JWT authorizer configuration.
Example
ts
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import * as bedrock_agentcore_alpha from '@aws-cdk/aws-bedrock-agentcore-alpha';
declare const gatewayCustomClaim: bedrock_agentcore_alpha.GatewayCustomClaim;
const customJwtConfiguration: bedrock_agentcore_alpha.CustomJwtConfiguration = {
discoveryUrl: 'discoveryUrl',
// the properties below are optional
allowedAudience: ['allowedAudience'],
allowedClients: ['allowedClients'],
allowedScopes: ['allowedScopes'],
customClaims: [gatewayCustomClaim],
};
Properties
allowedAudienceoptionalstring[]allowed_audienceoptionaltyping.List[str]allowedAudienceoptionalList<String>AllowedAudienceoptionalstring[]AllowedAudienceoptional*[]*string#Represents individual audience values that are validated in the incoming JWT token validation process.
Default: No audience validation
allowedClientsoptionalstring[]allowed_clientsoptionaltyping.List[str]allowedClientsoptionalList<String>AllowedClientsoptionalstring[]AllowedClientsoptional*[]*string#Represents individual client IDs that are validated in the incoming JWT token validation process.
Default: No client ID validation
allowedScopesoptionalstring[]allowed_scopesoptionaltyping.List[str]allowedScopesoptionalList<String>AllowedScopesoptionalstring[]AllowedScopesoptional*[]*string#Represents individual scopes that are validated in the incoming JWT token validation process.
Default: No scope validation
customClaimsoptionalGatewayCustomClaim[]custom_claimsoptionaltyping.List[GatewayCustomClaim]customClaimsoptionalList<GatewayCustomClaim>CustomClaimsoptionalGatewayCustomClaim[]CustomClaimsoptional*[]GatewayCustomClaim#Custom claims for additional JWT token validation.
Default: No custom claim validation
Allows you to validate additional fields in JWT tokens beyond the standard audience, client, and scope validations.
This URL is used to fetch OpenID Connect configuration or authorization server metadata for validating incoming tokens.
Pattern: .+/.well-known/openid-configuration Required: Yes