Metadata-Version: 2.1
Name: aws-cdk.aws-apigatewayv2-authorizers
Version: 1.116.0
Summary: Authorizers for AWS APIGateway V2
Home-page: https://github.com/aws/aws-cdk
Author: Amazon Web Services
License: Apache-2.0
Project-URL: Source, https://github.com/aws/aws-cdk.git
Description: # AWS APIGatewayv2 Authorizers
        
        <!--BEGIN STABILITY BANNER-->---
        
        
        ![cdk-constructs: Experimental](https://img.shields.io/badge/cdk--constructs-experimental-important.svg?style=for-the-badge)
        
        > The APIs of higher level constructs in this module are experimental and under active development.
        > They are subject to non-backward compatible changes or removal in any future version. These are
        > not subject to the [Semantic Versioning](https://semver.org/) model and breaking changes will be
        > announced in the release notes. This means that while you may use them, you may need to update
        > your source code when upgrading to a newer version of this package.
        
        ---
        <!--END STABILITY BANNER-->
        
        ## Table of Contents
        
        * [Introduction](#introduction)
        * [HTTP APIs](#http-apis)
        
          * [Default Authorization](#default-authorization)
          * [Route Authorization](#route-authorization)
        * [JWT Authorizers](#jwt-authorizers)
        
          * [User Pool Authorizer](#user-pool-authorizer)
        * [Lambda Authorizers](#lambda-authorizers)
        
        ## Introduction
        
        API Gateway supports multiple mechanisms for controlling and managing access to your HTTP API. They are mainly
        classified into Lambda Authorizers, JWT authorizers and standard AWS IAM roles and policies. More information is
        available at [Controlling and managing access to an HTTP
        API](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-access-control.html).
        
        ## HTTP APIs
        
        Access control for Http Apis is managed by restricting which routes can be invoked via.
        
        Authorizers, and scopes can either be applied to the api, or specifically for each route.
        
        ### Default Authorization
        
        When using default authorization, all routes of the api will inherit the configuration.
        
        In the example below, all routes will require the `manage:books` scope present in order to invoke the integration.
        
        ```python
        # Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
        authorizer = HttpJwtAuthorizer(...
        )
        
        api = HttpApi(stack, "HttpApi",
            default_authorizer=authorizer,
            default_authorization_scopes=["manage:books"]
        )
        ```
        
        ### Route Authorization
        
        Authorization can also configured for each Route. When a route authorization is configured, it takes precedence over default authorization.
        
        The example below showcases default authorization, along with route authorization. It also shows how to remove authorization entirely for a route.
        
        * `GET /books` and `GET /books/{id}` use the default authorizer settings on the api
        * `POST /books` will require the [write:books] scope
        * `POST /login` removes the default authorizer (unauthenticated route)
        
        ```python
        # Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
        authorizer = HttpJwtAuthorizer(...
        )
        
        api = HttpApi(stack, "HttpApi",
            default_authorizer=authorizer,
            default_authorization_scopes=["read:books"]
        )
        
        api.add_routes(
            (SpreadAssignment ...
              path
              path), /books=,
            method="get"
        )
        
        api.add_routes(
            (SpreadAssignment ...
              path
              path), /books/{id}=,
            method="get"
        )
        
        api.add_routes(
            (SpreadAssignment ...
              path
              path), /books=,
            method="post",
            authorization_scopes=["write:books"]
        )
        
        api.add_routes(
            (SpreadAssignment ...
              path
              path), /login=,
            method="post",
            authorizer=NoneAuthorizer()
        )
        ```
        
        ## JWT Authorizers
        
        JWT authorizers allow the use of JSON Web Tokens (JWTs) as part of [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html) and [OAuth 2.0](https://oauth.net/2/) frameworks to allow and restrict clients from accessing HTTP APIs.
        
        When configured, API Gateway validates the JWT submitted by the client, and allows or denies access based on its content.
        
        The location of the token is defined by the `identitySource` which defaults to the http `Authorization` header. However it also
        [supports a number of other options](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-lambda-authorizer.html#http-api-lambda-authorizer.identity-sources).
        It then decodes the JWT and validates the signature and claims, against the options defined in the authorizer and route (scopes).
        For more information check the [JWT Authorizer documentation](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-jwt-authorizer.html).
        
        Clients that fail authorization are presented with either 2 responses:
        
        * `401 - Unauthorized` - When the JWT validation fails
        * `403 - Forbidden` - When the JWT validation is successful but the required scopes are not met
        
        ```python
        # Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
        authorizer = HttpJwtAuthorizer(
            jwt_audience=["3131231"],
            jwt_issuer="https://test.us.auth0.com"
        )
        
        api = HttpApi(stack, "HttpApi")
        
        api.add_routes(
            integration=HttpProxyIntegration(
                url="https://get-books-proxy.myproxy.internal"
            ),
            path="/books",
            authorizer=authorizer
        )
        ```
        
        ### User Pool Authorizer
        
        User Pool Authorizer is a type of JWT Authorizer that uses a Cognito user pool and app client to control who can access your Api. After a successful authorization from the app client, the generated access token will be used as the JWT.
        
        Clients accessing an API that uses a user pool authorizer must first sign in to a user pool and obtain an identity or access token.
        They must then use this token in the specified `identitySource` for the API call. More information is available at [using Amazon Cognito user
        pools as authorizer](https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-integrate-with-cognito.html).
        
        ```python
        # Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
        user_pool = UserPool(stack, "UserPool")
        user_pool_client = user_pool.add_client("UserPoolClient")
        
        authorizer = HttpUserPoolAuthorizer(
            user_pool=user_pool,
            user_pool_client=user_pool_client
        )
        
        api = HttpApi(stack, "HttpApi")
        
        api.add_routes(
            integration=HttpProxyIntegration(
                url="https://get-books-proxy.myproxy.internal"
            ),
            path="/books",
            authorizer=authorizer
        )
        ```
        
        ## Lambda Authorizers
        
        Lambda authorizers use a Lambda function to control access to your HTTP API. When a client calls your API, API Gateway invokes your Lambda function and uses the response to determine whether the client can access your API.
        
        Lambda authorizers depending on their response, fall into either two types - Simple or IAM. You can learn about differences [here](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-lambda-authorizer.html#http-api-lambda-authorizer.payload-format-response).
        
        ```python
        # Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
        # This function handles your auth logic
        auth_handler = Function(self, "auth-function")
        
        authorizer = HttpLambdaAuthorizer(
            response_types=[HttpLambdaResponseType.SIMPLE], # Define if returns simple and/or iam response
            handler=auth_handler
        )
        
        api = HttpApi(stack, "HttpApi")
        
        api.add_routes(
            integration=HttpProxyIntegration(
                url="https://get-books-proxy.myproxy.internal"
            ),
            path="/books",
            authorizer=authorizer
        )
        ```
        
Platform: UNKNOWN
Classifier: Intended Audience :: Developers
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: JavaScript
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Typing :: Typed
Classifier: Development Status :: 4 - Beta
Classifier: License :: OSI Approved
Classifier: Framework :: AWS CDK
Classifier: Framework :: AWS CDK :: 1
Requires-Python: >=3.6
Description-Content-Type: text/markdown
