You're Invited:Meet the Socket Team at BlackHat and DEF CON in Las Vegas, Aug 4-6.RSVP
Socket
Book a DemoInstallSign in
Socket

scalper

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

scalper - npm Package Compare versions

Comparing version

to
0.0.1

example/passport-auth/app.js

5

package.json

@@ -5,3 +5,3 @@ {

"author": "Joe Wagner",
"version": "0.0.1-alpha",
"version": "0.0.1",
"scripts": {

@@ -11,2 +11,5 @@ "test": "NODE_ENV=test mocha"

"main": "index.js",
"dependencies": {
"node-uuid": "~1.4.1"
},
"devDependencies": {

@@ -13,0 +16,0 @@ "mocha": "~1.12.0",

15

README.md
scalper
=======
A socket.io authentication ticket store designed to allow an application to use an express app to do auth for a socket.io app
A ticket store designed to allow an application to use an express app to do auth for a socket.io app
Setup
=====
See `example/passport-auth/` for basic usage with express 4, passport, and socket.io. Notice the socket.io server and the express server are completely separated. They could potentially be hosted on separate domains without issue.
Worth noting that the example uses http for simplicity, but its recommended to use https.
Motivation
==========
There are many advantages for token based authentication when using websockets.
Heroku docs have a [nice article](https://devcenter.heroku.com/articles/websocket-security) outlining some of the details of securing websockets.
[authO.com](https://auth0.com/blog/2014/01/15/auth-with-socket-io/) has a blog post that also goes over the details of token based auth with socket.io