Devise Token Auth VS react-on-rails

I have a React single page application using React Router that hooks into a Rails 5 API. The Rails application uses devise_token_auth for authentication. I've successfully created an authentication process that stores the user state in a Redux store on the client side.

Did you send an authorization header with your api call? The error is pretty clear — the request is unauthorized. Devise is expecting session cookies, but your api should use tokens. https://github.com/lynndylanhurley/devise_token_auth

I mentioned Identity in my first comment. I've never found it as simple as Devise though - especially in an API only setting.

With Devise there's a third-party Gem you can use called devise_token_auth which deals with everything automatically.

https://github.com/lynndylanhurley/devise_token_auth

redux-token-auth is a great library. What it mainly does is it provides a plug and play auth implementation functionality for ruby on rails based APIs which implement popular devise_token_auth for auth handling.

have you looked at https://github.com/waiting-for-dev/devise-jwt or https://github.com/lynndylanhurley/devise_token_auth

I'd prefer to have a standalone rails API and a react client separately, but that's not mandatory. I discovered a gem called devise_token_auth and it didn't seem to have refresh tokens but it refreshed the tokens on every request anyway so I was pretty happy with it.

As a side note, also check out devise_token_auth here

You should take a look at https://github.com/shakacode/react_on_rails. I created that repo back in 2015 and it's still going strong. Popmenu.com uses it and we've got 5,000 restaurant chains on the Rails monolith and huge traffic and transaction volume. Check out the html source of a popmenu site, like https://110grill.com. You'll see react-on-rails in the source.

It's me, Justin, the guy the started React on Rails and React on Rails Pro many years ago! I'll be following this thread!

The problem is I have no idea how to implement the "remember me" feature in that gem without just making the tokens not refresh for a very long time (I think that would be a security concern). So then I looked more into react_on_rails to just use sessions with Devise as a normal rails app, but I don't know if I'll be able to deploy that on AWS because of the changes I have to do to the webpacker/webpack config to allow for a better folder structure. I've never done that so I don't know if there may be any issues.

I have a production level Ruby on Rails app that is slowly transitioning from pure Rails with JS sprinkles to a Rails backend and React frontend kind of situation using React on Rails.

https://github.com/shakacode/react_on_rails - It was last updated 2 months ago & can do prerendering. I'm not sure why more people aren't suggesting this.

https://github.com/shakacode/react_on_rails use this instead. It's maintained and preferred nowadays

React on Rails is an integration of React + Webpack + Rails + rails/webpacker including server-side rendering of React, enabling a better developer experience and faster client performance. 4,558 stars by now