Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to use the same controller for browser users (form-based auth) and OAuth API users. Seems like gems like doorkeeper make controllers accept only OAuth 2.
Should I make a basic no-auth controller and two subclasses (one for OAuth, another for form-based)? Or is there a solution that allows it on one controller class?
The oauth-plugin allows this. You can specify:
This will allow both logged in users, and OAuth users to access the same controller actions.
I wrote a blog post on setting up an OAuth2 provider with oauth-plugin. You can follow it for the most part, however you probably don’t want to have an API base class, and you want to replace:
With: