Skip to content

Support warden based authentication #4

Closed
vanstee opened this Issue Jul 16, 2012 · 1 comment

1 participant

@vanstee
Owner
vanstee commented Jul 16, 2012

We should take advantage of all the cool things rack gives us for free including middlewares like warden. Instead of implementing our own authentication methods we should just delegate to warden. I figure we can authenticate with scopes conveniently named after the models of "controller" the request is talking to.

For this to work I think we just need to generate a before filter that authenticates and then a detailed description in the README.

Couldn't hurt to add it to http://github.com/vanstee/hovercraft_example

@vanstee
Owner
vanstee commented Jul 30, 2012

I think just adding basic global support is ok for now. The ability so swap out Hovercraft::Filters and Hovercraft::Routes would be a better solution for people who need something crazy.

@vanstee vanstee closed this Jul 30, 2012
@vanstee vanstee added a commit that referenced this issue Jul 30, 2012
@vanstee Authenticate requests with warden
If the warden instance is availble in the current session, use it to
authenticate the request. Warden is setup outside the hovercraft server
at the rack layer. This just adds a global filter instead of resource or
route specific ones. Closes issue #4
12f887f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.