-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Authentication login into concern #106
Comments
Yeah, I'd like to see this, too. It'd allow it to fully work with other gems like https://github.com/collectiveidea/audited out-of-the-box. |
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into an issue when trying to use authentication-zero with Avo Admin. They do not inherit from application controller::base so the current_user is not available. I had to move the authentication logic into a concern so I could include it in both places.
This is the solution that I ended up with. I propose that we move this authentication logic into a concern so it can more easily be extended and also better organizes the application controller for projects.
Would it be possible to make current_user work in the same way it does in devise so that way Avo would work out of the box with authentication zero without having to prepend anything?
The text was updated successfully, but these errors were encountered: