-
Notifications
You must be signed in to change notification settings - Fork 232
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
Adding authorizer field to collect context properties from authorizer #77
Conversation
Let me know if we need to keep non-String types specifically for Authorizer context. I'll change it to |
+1 to trying to get this added. For people trying to use this library for Cognito User Pool integration (or other types of authorization), it's a non-starter. |
@bmoffatt could you please take a look & share your thoughts? Thanks |
@avanathan |
@bmoffatt I've switched it to |
Thanks! |
@bmoffatt When do we usually cut a release? |
…aws#77) * Adding authorizer field to collect context properites from authorizer * Updating toString() method * Adding authorizer to equals() & hashCode() * Moving authorizer under ProxyRequestContext * Switching to Map<String, Object> for authorizer
Issue #, if available:
Reopening: #39
Description of changes:
Adding a map to hold context properties from authorizer. cc: @bmoffatt @oharaandrew314 @miere . This PR was originally submitted by @oharaandrew314 and got closed based on a review comment for using
String
key/values. All other collection fields in this class useMap<String, String>
. Not sure why we need to worry about other types (nonString
) just for this. We could keep this in the short term until we find a long term solution. Libraries for rest of the programming languages like golang & .Net already support this. Thanks for your support.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.