Aurel Branzeanu

I am still seeing 'Started GET "/users/sign_in"' in your log. This is wrong - you are doing Resource Owner Password Credentials Grant Flow, so to get the access_token you should...

Try to comment this too: devise_scope :user do post 'users/finish_sign_up', :to => 'registrations#finish_sign_up' get 'users/finish_sign_up', :to => 'registrations#finish_sign_up' end And, to get things clear, the login page should not do...

As you want OAuth with Doorkeeper, I already told you that the sign-in should be performed on oauth/token - take a look at [Doorkeeper's API endpoint descriptions and examples wiki...

Ah, well. you're right, sorry! Sign in/up mess into my brain (english is non-native for me) :) For sign up (and also for list, update, remove,) you'll make a Grape...

Not at all - this is intentionally for confirmations from users to devise to work: devise_for :users, only: :confirmations, defaults: { format: :json }

That's right. When you will add and mount a Grape Users controller, you will define all these users' actions in it and the routes will appear again.

To see Grape roots, use this gem - https://github.com/texpert/grape_on_rails_routes

Made a PR using Doorkeepers authenticate_admin - https://github.com/antek-drzewiecki/wine_bouncer/pull/64

Ngrok v3 support has just landed in the new release of my fork and expansion of this gem - `ngrok-wrapper` - https://github.com/texpert/ngrok-wrapper/releases/tag/v0.3.0

If anybody's interested, I have forked this repo and crafted a new gem, implementing the `ngrok` process reusal found in another fork (everything described in the `History` chapter of my...