-
Notifications
You must be signed in to change notification settings - Fork 2
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
Authentication as a middleware #36
Comments
Closed
tracend
added a commit
that referenced
this issue
Dec 13, 2012
tracend
added a commit
that referenced
this issue
Jan 11, 2013
tracend
added a commit
that referenced
this issue
Jan 13, 2013
tracend
added a commit
that referenced
this issue
Jan 13, 2013
tracend
added a commit
that referenced
this issue
Jan 13, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Building the authentication for the library has become a body of its own.
As it is gearing out of the core scope for the library, and keeping node principals that are specialised in one thing, it is reasonable to suggest that the oauth server needs to be externalised as a separate module.
On the downside, the lib will come with no authentication process by default - but it can look out for middleware that will handle authentication during the connect() request....
The text was updated successfully, but these errors were encountered: