You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Etherpad-Lite has functionality that can require pads to be connected to with a cookie. That cookie is typically retreived by a third-party app via the API and assigned via the same third-party app. ANY form of authentication/security would be great to see.
Etherpad-Lite has a users/groups model that I think works quite well.
The text was updated successfully, but these errors were encountered:
Firstly, to get it off my chest... Etherpad Lite is now called Etherpad. ;) @cooperq you might want to change the description
Our session / auth implementation is not great. You can't restrict editing of specific parts of a document etc. The implementation itself is a bit weird too..
You are welcome to implement a similar system but be mindful of the caveats :)
So our thought on this was that if there was an authentication layer it should be seperate from ethersheet. I don't want to encumber ethersheet with a bunch of auth crap. My security model for this is that the URLs are impossible to guess. I think I would rather add the ability to change a sheet's URL and some form of client side encryption for spreadsheets than an auth system.
Etherpad-Lite has functionality that can require pads to be connected to with a cookie. That cookie is typically retreived by a third-party app via the API and assigned via the same third-party app. ANY form of authentication/security would be great to see.
Etherpad-Lite has a users/groups model that I think works quite well.
The text was updated successfully, but these errors were encountered: