devise_token_auth | Token based authentication for Rails JSON APIs | Authentication library

Ok, I missed this before_action method:

https://github.com/lynndylanhurley/devise_token_auth/blob/c92258038c05fcc8f6a0374ccce2e63b9f8d5312/app/controllers/devise_token_auth/concerns/set_user_by_token.rb#L26

This is where it takes your headers, checks them and sets instance variables.

By finding this I realized I was not sending the headers that I thought I was sending. I changed my http request it works fine.

axios.get('api/v1/auth/sign_out', headers)

Side Note: The logout action by default in devise is delete but this can be modified:

Maybe this might be useful to someone. The token comes in the header not the body.

Update:

I also needed to work around client side cors issues.

A few options that helped:

Vue Axios CORS policy: No 'Access-Control-Allow-Origin'

https://blog.bitsrc.io/how-and-why-you-should-avoid-cors-in-single-page-apps-db25452ad2f8

The easiest solution was executing chrome the command line:

open -n -a /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --args --user-data-dir="/tmp/chrome_dev_test" --disable-web-security

Source: https://alfilatov.com/posts/run-chrome-without-cors/

A couple of things...

1. Omniauth callbacks controller is missing the redirect information (is that why that note is there?). If you're using Devise, it should say something like sign_in_and_redirect @user underneath the @user = ... line.
2. Devise comes with built in routes. To use them, you must include something like, devise for :users in your routes.rb file. Check out the "Devise_for magic" section on this page to see an example of these built in routes. Note that you have to have some Devise models configured for this to work.
3. Run rake routes to see if the routes you have defined are what you're expecting.
4. If you can't figure it out, I also created a project using Omniauth and devise. You can view my code here.

Silly error on my part.

I just needed to change curl -XGET to curl -v -XGET to display the headers, which included the tokens.

I found the solution

I send slug_id with the uid, access_token and client for subscribing to the channel and I use it in connection.rb like this

you can override the DeviseTokenAuth::ConfirmationsController#show and redirect to root_path

DeviseTokenAuth ConfirmationsController#show