networknt / networknt/light-aws-lambda
How to deploy the jwt-authorizor in a separate stack
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If lambda-framework is used, the jwt-authorizer should be used along with AWS API Gateway to authorize the JWT token and enrich the scopes so that the lambda function can verify the scope against the specification. We can deploy the jwt-authorizer to most regions and let the users use the shared lambda function or allow users to deploy on their own.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AWS API Gateway, jwt-authorizer, and shared Lambda deployment concepts named in the issue. Clarify whether the intended result is deployment guidance, a separate-stack implementation, or both, and document the supported shared and user-owned deployment paths once the approach is decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- authentication, authorization, cloud
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100