24 Commits (a2d250412eb9e4d603721b43f151bf85254bb3bc)

Author	SHA1	Message	Date
Rodrigo Nascimento	b5168d3e62	Fix removal of users from room	9 years ago
Martin Schoeler	bbffa3b1ac	fixed wrong method name	9 years ago
Martin Schoeler	d12f25f82a	check if the user being removed is the last owner of the room	9 years ago
Martin Schoeler	6116da9099	no message	9 years ago
Diego Sampaio	249d99e8bf	Add some basic validation to if user is logged in	10 years ago
Marcelo Schmidt	7556b14135	Use new error format	10 years ago
Marcelo Schmidt	efdffa9407	Do for owners as for moderators	10 years ago
Marcelo Schmidt	eaf025ec37	Rework	10 years ago
Diego Sampaio	7cac1c4b2a	removed all console.logs from publishes and methods	10 years ago
Marcelo Schmidt	53e93aa86c	/kick command and button for kicking users from room	10 years ago
Rodrigo Nascimento	3a664a92bd	Replace part of ChatMessage.insert	10 years ago
Rodrigo Nascimento	cc12274dc6	Replace all ChatRoom.update	10 years ago
Rodrigo Nascimento	d7f78988a5	Replace all ChatRoom.findOne	10 years ago
Rodrigo Nascimento	647312aeaa	Replace all ChatSubscription.remove	10 years ago
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
Rodrigo Nascimento	e56c2238c3	Replace all Meteor.users.findOne	10 years ago
Gabriel Engel	29db81dfee	replacing "by" for "u"	11 years ago
Rodrigo Nascimento	4d2db614b7	More adjustments	11 years ago
Diego Sampaio	4fd5bea08e	removed auto room rename on based on room's members	11 years ago
Rodrigo Nascimento	5e546e78c0	Remove logs	11 years ago
Diego Sampaio	fc7f3180cf	all room types	11 years ago
Gabriel Engel	66d2c9b45a	Proudly making the real initial commit! Congratulations to all involved: Diego Sampaio, Marcelo Schmidt, Rafael Caferati and Rodrigo Nascimento	11 years ago