It should be possible to lock down a sharejs server, and restrict read / edit access t

Waiting on issue <a class="issue-link js-issue-link" data-error-text="Failed to load t

Documentation: <a href="https://github.com/josephg/ShareJS/wiki/User

Authentication about sharejs HOT 6 CLOSED

josephg commented on August 22, 2024

Authentication

from sharejs.

Comments (6)

josephg commented on August 22, 2024

Waiting on issue #18 , because socket.io 0.7 has a way sweeter authentication mechanism.

from sharejs.

josephg commented on August 22, 2024

In progress - I've got it vaguely working in head, though its exposing various bugs in the client and stuff. Docs in the wiki.

from sharejs.

josephg commented on August 22, 2024

Documentation:

https://github.com/josephg/ShareJS/wiki/User-access-control

from sharejs.

josephg commented on August 22, 2024

Authorization code: COMPLETE! Wewt! happy dance

Now if you try and edit any document with the exampleserver which has a name starting with 'readonly', your ops get rejected. The protocol isn't telling the client that the document is readonly yet. When the ops are rejected the document is reverted after a single server round-trip. Its cool :D

from sharejs.

josephg commented on August 22, 2024

.... This still isn't implemented for the REST interface.

from sharejs.

josephg commented on August 22, 2024

... Aaaaand fixed.

from sharejs.

Recommend Projects