Sorcery
authentication-zero
Sorcery | authentication-zero | |
---|---|---|
10 | 15 | |
1,413 | 1,318 | |
0.8% | - | |
5.8 | 8.0 | |
4 days ago | 2 months ago | |
Ruby | Ruby | |
MIT License | 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.
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?
-
Build a password authentication feature with Sorcery gem.
I made a 8 minutes video tutorial (following the wiki: https://github.com/Sorcery/sorcery/wiki/Simple-Password-Authentication) to introduce how to build a simple password authentication feature with Sorcery. With some minor modification to please Turbo.
-
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.
-
Easy has_secure_password API authentication
sorcery
authentication-zero
-
An Introduction to LiteStack for Ruby on Rails
Subsequently, we need a way to authenticate our users to associate prompts with them. Rather than using an incumbent like Devise, I chose to use a different approach. The authentication-zero gem can flexibly generate an authentication system, as opposed to including it as an engine. Conveniently, it comes with options such as:
- Generate a pre-built authentication system into a rails application
-
Everything was going great until I installed Devise!
If you don’t need a good amount of features that Devise brings to the table, I‘d skip it entirely. Look up has_secure_password, that will be enough for a vast amount of applications with authentication. Maybe combine with cancancan for authorization. Once you feel you have a grip on those, re-evaluate devise or take a look at https://github.com/lazaronixon/authentication-zero which will transparently integrate into your app instead of providing a Rube Goldberg machine (that’s what devise will feel like for beginners for a long time).
-
Authentication, Roles, and Authorization... oh my.
I keep going back and forth between Devise and something a little more friendly like authentication-zero gem for authentication.
-
Upgrading authentication-zero gem in project
For those that have used the authentication-zero gem or are familiar with its functionality, what is the best way to upgrade it in a project when new functionality is released?
- An authentication system generator for Rails applications.
- For Rails API-only authentication, do you go for a gem or 3D party service?
-
An Overview of Ruby on Rails 7.1 Features. Part III
True. I tend to stay away from gems that try to integrate into multiple parts of your app to provide some sort of comprehensive solution. The kinds of gems I recommend are: 1) libraries (you call into them when you need them) 2) mounted apps on a url, isolated from the rest of your app 3) generators (this one seems nice, the author mentioned it in another HN thread: https://github.com/lazaronixon/authentication-zero).
-
why is devise industry standard?
Check out https://github.com/lazaronixon/authentication-zero
-
Time to think about swapping off Devise?
I prefer to use authentication-zero, which generates code for me in the same application using has_secure_password, has good security practices, uses the same functions as Rails, and allows me to modify the flow to my liking.
What are some alternatives?
Devise - Flexible authentication solution for Rails with Warden.
devise - Flexible authentication solution for Rails with Warden.
Clearance - Rails authentication with email & password.
OmniAuth - OmniAuth is a flexible authentication system utilizing Rack middleware.
rails_mvp_authentication - An authentication generator for Rails 7. Generate all the files needed to create a feature rich authentication system that you control. No configuration needed.
Authlogic - A simple ruby authentication solution.
JWT - A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
Devise Token Auth - Token based authentication for Rails JSON APIs. Designed to work with jToker and ng-token-auth.
Knock - Seamless JWT authentication for Rails API
genkan - :door::running:Genkan is authentication engine for Rails