RE: Hey, really loving jets so far
Thanks for the kind words!
RE: but I’m not able to find any strong examples of auth. So far I’ve tried porting devise to Jets without much success and using the built-in Cognito support, but neither has seemed to work.
Don’t have a turnkey auth example yet. Unsure when will get to it, it’s matter of time. Glad that you’ve been looking at porting devise though. Thinking it would be nice if there was turnkey approach for both:
- Traditional auth - devise-like or something. This is probably what most are used to.
- Cognito auth - The more serverless approach.
For the traditional auth, devise may be a decent place to start for design and overall flow. Thinking it will require a bunch of changes.
For Cognito, others have had some success using Amplify in front: Cognito Support? - #5 by heythisisnate - Jets - BoltOps Community Though, as you pointed out, the local testing story needs improvement: requestContext & Cognito Authorization - Jets - BoltOps Community
Here’s some history. Added the authorizer concept a while back.
- Initial request with a detailed issue report Support ApiGateway Lambda Authorizer · Issue #361 · rubyonjets/jets · GitHub
- Implemented a slightly different syntax in PR: API Gateway Authorizer Concept Support by tongueroo · Pull Request #368 · rubyonjets/jets · GitHub
- Fixes Support ApiGateway Lambda Authorizer · Issue #361 · rubyonjets/jets · GitHub
- More fixes clean up authorizers and bug fixes by tongueroo · Pull Request #369 · rubyonjets/jets · GitHub
Will have figure out a better way to test locally. In addition, will have to figure out a more turnkey quick-and-easy example.
Will consider PRs for this. Of course, no sweat either way 