#178

[@SupeRails]

🚨 The updated syntax is to use `bin/rails generate authentication`, not `bin/rails generate sessions`

[@julian_handpan]

Finally! Something that make more sense than fight with JS...

[@SupeRails]

In what case are you fighting with JS on authentication?

[@julian_handpan]

@@SupeRails I mean make more sense, since everyone need auth. And JS keeps changing…

[@ゆうた-f2o]

テストするまでは今まで通り自前のログイン機能かdevice使い続けると思うけど新しい認証増えてるのは嬉しい😊

[@yaroslavbozhak9107]

Great. Thanks for useful info.

[@indigotechtutorials]

Loved this video and I appreciate the tips about using the main branch and getting access to this feature I wonder if there is a good tailwind template or that woudl be a good idea for a new gem

[@SupeRails]

There's a place for that! github.com/rails/tailwindcss-rails/issues/382

[@haroldpepete]

great video, do you think apart from basic authentication rails would implement oauth out of thee box?

[@SupeRails]

I really really doubt that

[@ledockol]

Спасибо Ярослав за интересное и познавательное видео.

[@SupeRails]

все для вас, дорогі друзі :)

[@idreesibrahim5642]

please use following command for now. "bin/rails generate authentication" sessions has swapped with authentication

[@SupeRails]

Right!!!

[@hellomynameisbenjaminupton]

Glad I found this comment.. Thanks

[@Helisltu]

Why storing session in cookies is better than storing in session?

[@SupeRails]

@@Helisltu this might explain www.rubanonrails.com/2/cookie-based-authentication-with-rails/20/secure-session#http-only-cookies

[@yoyobroker8107]

Hilarious thumbnail 😄 Great video 👍

[@SupeRails]

Thanks bro. Although it's a bit misleading. Devise is very good, and it's going nowhere any time soon!

[@MidSeasonGroup]

@superails please revisit and expound on this built-in feature.

[@Pablo-Herrero]

Is there any good reason to do this? Is the Devise gem dead or troublesome in some way?

[@SupeRails]

No, I do not recommend to use this solution! Devise is perfectly good. I recommend Devise!

[@hiphopheadninethree]

Can you do video on how to handle email verification before allowing access to account

[@SupeRails]

@@hiphopheadninethree if you are using Devise, use Devise confirmable (Episode 41): superails.com/posts/ruby-on-rails-41-devise-confirmable-no-more-users-with-fake-emails If you are using this (rails 8 authentication), try this: railsbytes.com/public/templates/Xg8sMD !! Curently I do not recommend using Rails 8 native authentication in production. It is 💩 comparing to Devise

[@NoobCodeSaga]

Great!

[@SupeRails]

To be clear, I do not recommend you to use this new Rails auth generator. Devise is way better!

[@stpaquet]

I like to reuse the same conventions as the ones used in Devise. So usually I will have current_user and same for the methods so that I can reuse other gems without any charge (Authorization or Access control for example)

[@SupeRails]

I also like the devise naming. But.... I don't recall of any other gems that rely on having methods like "current_user"...?

[@stpaquet]

@@SupeRails Pundit is one. Also many examples for Rolify are based on the Devise conventions (unlike Pundit, I do not think that they are enforcing the conventions)

[@tofuman9526]

So what you do for oauth?

[@stpaquet]

@@tofuman9526 OAuth2 gem or doorkeeper.

[@mikopiko]

Finally!

[@SupeRails]

I think we still need to wait a bit for this to be production-ready

[@tofuman9526]

What about OAuth implementation?

[@SupeRails]

Check out episode #103 Simple Omniauth without Devise. That's what I use for superails.com/