serverless / serverless/examples
[Auth0 Custom Authorizers] Best practice for storing/accessing public key in production?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 4.4k
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 3
Description
I'm following this example.
What would be the recommended way to store and access the public key in production? Check it in to version control? I know that I can sls deploy, but what if I want to use CI (in this case https://seed.run)?
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 with the linked aws-node-auth0-custom-authorizers-api example and review how its public key is currently supplied during deployment. Compare that approach with the stated CI use case at Seed; done means documenting a production-safe storage and access recommendation for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- authentication, cloud, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100