Skip to content
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

Backends should have access to socket #1

Closed
scttnlsn opened this issue Dec 1, 2011 · 1 comment
Closed

Backends should have access to socket #1

scttnlsn opened this issue Dec 1, 2011 · 1 comment

Comments

@scttnlsn
Copy link
Owner

scttnlsn commented Dec 1, 2011

Authorization should happen at the level of the backend since using Socket.IO's authorization mechanism does not offer enough granularity. As an example, consider a backend that allows anyone to read but only logged in users to create, update or delete. By providing the backend with a socket, it could optionally obtain the session ID and authorize the current operation.

@scttnlsn
Copy link
Owner Author

scttnlsn commented Dec 1, 2011

Experimenting on the auth branch:
https://github.com/scttnlsn/backbone.io/tree/auth

@scttnlsn scttnlsn closed this as completed Dec 2, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant