Skip to content

Support for IAM Policy for Lambda Authorizer (v1) #184

Closed

Description

@missourian55

Appreciate you guys added few event types to support the LambdaAuthorizer, Any plans to add a event type for IAM policy response which will be compatible with REST API?

Currently I am using this class from blueprints
https://github.com/awslabs/aws-apigateway-lambda-authorizer-blueprints/blob/master/blueprints/java/src/io/AuthPolicy.java

APIGatewayCustomAuthorizerEvent (Rest) 
APIGatewayV2CustomAuthorizerEvent (http)
SimpleIAMPolicyResponse (http)
IAMPolicyResponse (rest) <---- missing

Activity

  1. msailes commented on Nov 2, 2020

    @msailes
    Contributor

    Hi missourian55,

    Yes, there is an open PR for this response. #174

    Mark

  2. missourian55 commented on Nov 6, 2020

    @missourian55
    Author

    Any ETA on when this will be merged and released? We love to have this soon to remove some custom implementation in our stack.

  3. msailes commented on Dec 31, 2020

    @msailes
    Contributor

    Hi missourian55,

    For a couple of reason this is proving a little annoying. In the short term I would continue to use the AuthPolicy class.

    Please reply back if you have any questions.

  4. msailes commented on Mar 24, 2021

    @msailes
    Contributor

    This has been released in version 3.8.0

  5. missourian55 commented on Mar 25, 2021

    @missourian55
    Author

    Just gave IamPolicyResponse a try on Rest API. Getting below error

    Execution failed due to configuration error: Unable to parse given policy: Syntax error at position (-1,-1)

    {"principalId":"some","policyDocument":{"Version":"2012-10-17","Statement":[{"Condition":null,"Action":"execute-api:Invoke","Resource":["arn:aws:execute-api:us-east-1:123456789012:hr2mbvlnw6/some/POST/somemethod"],"Effect":"Allow"}]},"context":null}

    I cannot use IamPolicyResponse with REST API? Its only for Http API (API GW V2)?

  6. msailes commented on Mar 25, 2021

    @msailes
    Contributor

    My apologies, the response required for the REST API has an additional field "usageIdentifierKey": "{api-key}" and is a required field.

    I'll create a new PR.

  7. missourian55 commented on Mar 25, 2021

    @missourian55
    Author

    @msailes Thanks for looking into this. Currently we are using AuthPolicy for REST api and we never populated usageIdentifierKey. Is this a new breaking change?

    If I need to populate this where I should get this value from?

  8. msailes commented on Mar 25, 2021

    @msailes
    Contributor

    Do you have an example handler that you can share which exhibits this error?

  9. missourian55 commented on Mar 25, 2021

    @missourian55
    Author

    is it possible to share in any private mode? Otherwise I need to do lot of scrubbing to eliminate my company info

  10. msailes commented on Mar 25, 2021

    @msailes
    Contributor

    You can contact me on my username @amazon.co.uk

  11. missourian55 commented on Mar 25, 2021

    @missourian55
    Author

    Done

  12. wilerson commented on May 21, 2021

    @wilerson

    Any ETA on merging and releasing #233 ?

  13. msailes commented on May 26, 2021

    @msailes
    Contributor

    @wilerson we hope to release this in June.

  14. msailes commented on Jun 2, 2021

    @msailes
    Contributor

    this has been released in v3.9.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions