UsageIdentifierKeys added into AuthResponse for use in Built-In Authorizers #2129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added in a
usageIdentifierKey
attribute into theAuthResponse
class and modified theto_dict
method to serialize it if it exists. This allows my built-in authorizer to inject API Key values for tracking in Usage Plans. My use case involves translating existing header values into API Keys, instead of forcing my clients to provide an additional header and key.Issue #, if available:
Description of changes:
app.py AuthResponse class updated to add the attribute in the contstructor and serialize in the to_dict method.
tests/test_app.py updated to include test case where usageIdentifierKey attribute is used.
docs/api.rst updated to reflect the new attribute.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.