The communications platform that puts data protection first.

hacktoberfestcollaborationfossjavascriptmeteorreal-timewebrtcmitslackchatfree

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Reid Wakida c2e6e0fa2c Create RocketChat authorization package that handles role and permission ... based authorization Leverages alanning:roles package to associate a user to a role. Uses alanning:roles optional "group" parameter to limit the role's scope to either the global level or room level. The global level is applicable to users that can perform administrative functions. The room level is applicable to users that can perform room specific administrative functions (like a moderator). A role can have zero or more permissions. Permissions and their association to roles are defined by this package Authorization checks are based on whether or not the user has a role or permission. The roles, permissions, and their association are statically defined at this time. Eventually, there should be an API to dynamically create a role and associate it to static permission(s). Old 'isAdmin' and '.admin is true' checks have been replaced with corresponding hasPermission authorization checks. Additionally, code that automatically assigned admin privileges are updated to assign 'admin' role instead. channel/direct message/private group code checks authorization to edit properties (e.g. title) and edit/delete messages (regardless of the system level allow edit/delete settings). - user with 'admin' role are authorized to do anything - room creator is assigned 'moderator' role that can edit the room and edit/delete messages - members can only edit/delete their own messages IF system wide settings permit them to. v19 migration will - add 'admin' role to users with admin:true property - add 'moderator' role scoped to room for room creators - add 'user' role to all users. There are known issues unrelated to the changes made - If a user with edit/delete message room permissions logs out then a user without edit/delete message room permissions logs in, then they will see edit/delete icons. The server will deny execution - edit/delete icons are not reactive Thus if the system level allow edit/delete message setting is toggled, the icons will not reflect it. The server will deny execution.		10 years ago
..
migrations	Create RocketChat authorization package that handles role and permission	10 years ago
appcache.coffee	Appcache config	11 years ago
avatar.coffee	adding in user icon in the desktop notifications	10 years ago
cron.coffee	Merged statistics / changed method name	10 years ago
i18n-validation.coffee	Disable i18n validation message	11 years ago
indexes.coffee	Initial implementation of search in channel	10 years ago
initialData.coffee	Create RocketChat authorization package that handles role and permission	10 years ago
presence.coffee	Register process port into Instance Status	11 years ago
settings.coffee	Proudly making the real initial commit! Congratulations to all involved: Diego Sampaio, Marcelo Schmidt, Rafael Caferati and Rodrigo Nascimento	11 years ago