-
Notifications
You must be signed in to change notification settings - Fork 239
APIGatewayProxyRequestEvent does not have authorizer #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I second this, any news on this? |
Yes, I made a PR in #39 |
@onema, in the meantime, you can do what I do and redefine the file in your project. If you use the exact same package, it should override the version in the library. |
It would be nice if the authorizer was exposed. Since the values can be anything, perhaps setting them to It seems the go library uses this approach: https://github.com/aws/aws-lambda-go/blob/v1.2.0/events/apigw.go#L36 |
@oharaandrew314 Could you pls. reopen PR #39 ? Everyone making changes in their code repo for a generic change is not a scalable solution. Thanks! |
@avanathan I'm no longer using lambdas with Java, so I believe I'd be a poor champion for the PR. If you wish, feel free to copy my changes and make your own PR. You may have the modify the map to use Object though. It does seem that you can get non-string values in some cases; though I have never encountered any. |
@oharaandrew314 Thanks. I did open a PR - #77, but kept it |
This was released as part of version |
The
APIGatewayProxyRequestEvent
requestContext
object does not have theauthorizer
object. With the new addition of the authorizer context, I am unsure how to structure a newAuthorizer
object.It is entirely possible to have an authorizer json blob like:
The
principalId
is always part of theauthorizer
blob, and thus should be a String field on a newAuthorizer
object. However, the additional arbitrary parameters provided by the authorizer context should be a map. This won't (de)serialize 1:1 between JSON and Java however.The text was updated successfully, but these errors were encountered: