decent_authentication
Sorcery
Our great sponsors
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Onboard AI - Learn any GitHub repo in 59 seconds
- SaaSHub - Software Alternatives and Reviews
decent_authentication | Sorcery | |
---|---|---|
1 | 10 | |
20 | 1,374 | |
- | 0.5% | |
0.0 | 0.0 | |
9 months ago | about 1 month ago | |
Ruby | Ruby | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
decent_authentication
-
Why there is no simple default auth in Rails?
I built an example rails project that shows how to use it here if you want to check it out: https://github.com/leesmith/decent_authentication
Sorcery
-
Everything was going great until I installed Devise!
I have been using devise for a while and it has consistently given me issues. I have wistfully been staring at sorcery for a while now but cant justify the switch since devise is already in the project.
- What is used for authentication in Rails nowadays?
-
Authentication with Sorcery, RSpec, and Rails 7: Building a simple Rails CMS - Part 1
We'll be installing Sorcery based off this tutorial in their wiki. I'm modifying a little bit since we are creating something different, but also because their tutorial is a bit outdated since it is based off an older version of Rails.
- Webpacker Retired
- What are your top useful gems?
-
A November of WTFs
But does it have to be so soon? There are other areas where I'm just as ignorant as I was about the inner workings of authentication (see "the database" below), and in these areas there's not a gem that can automatically solve the problem for me—which is what I've ended up doing for authentication in my own project: even though I could build authentication from scratch, instead I'm using an authentication gem because the effect is exactly the same, but with less code in my app for me to maintain. (Rather than Devise, I've chosen the more lightweight alternative Sorcery. It's simple enough that I can still understand and control the authentication flow, while also providing enough conveniences that I don't have to write out implementation details from scratch.)
-
Why there is no simple default auth in Rails?
Also Sorcery is, despite its name, a little less magic than Devise.
Rails doesn’t even have a user model by default as opposed to Django (in the past) because Auth is very much dependent on your app. There’s devise for when you need batteries included and if that’s too much there are smaller gems like https://github.com/Sorcery/sorcery
-
Easy has_secure_password API authentication
sorcery
What are some alternatives?
Devise - Flexible authentication solution for Rails with Warden.
Clearance - Rails authentication with email & password.
OmniAuth - OmniAuth is a flexible authentication system utilizing Rack middleware.
Authlogic - A simple ruby authentication solution.
JWT - A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
Knock - Seamless JWT authentication for Rails API
Doorkeeper - Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.
warden - General Rack Authentication Framework
Devise Token Auth - Token based authentication for Rails JSON APIs. Designed to work with jToker and ng-token-auth.
Monban - Oath is rails authentication made simple. Previously known as Monban
genkan - :door::running:Genkan is authentication engine for Rails
passwordless - 🗝 Authentication for your Rails app without the icky-ness of passwords