allow customisation of the JWT fetcher #88
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.
Issue #86
Description of changes:
Allows customisation of the JWT fetcher. Mainly desired so that the 1500ms default responseTimeout can be increased to 5000ms, which has been the source of this issue #86. I have forked this repo and deployed the changes with a 5000ms to my lambda@edge and now the cognito flow and redirection works as expected, whereas previously I was getting timeout errors, the source of which was verifying the JWT.
Its effecteively just allowing this https://github.com/awslabs/aws-jwt-verify#configuring-the-jwks-response-timeout-and-other-http-options-with-jsonfetcher
Some related issues that I found useful: awslabs/aws-jwt-verify#133 and in particular awslabs/aws-jwt-verify#72
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.