You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2014/06/08 17:48:02 UTC

[jira] [Updated] (OPENMEETINGS-1017) ACLs should be added to the User

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik updated OPENMEETINGS-1017:
-------------------------------------------

    Description: 
Hello All,

Due to multiple requests and issues (please see [1], [2], [3]) I would like to change User object (remove status and "user level") and add Permissions.

As I can see the permissions should be
Admin       == access to Admin module
Room        == enter the room
Dashboard == access the whiteboard
Login         == login to Om internal DB
Soap         == use rest/soap calls

for example 
current "regular" user will have all permissions except for Admin and Soap
current "soap" user will have soap permission only
current OAuth user will have no Login parmission

The proposed system looks extendable and should cover all current needs

I'm going to implement it in 3.0.3 and 3.1.0

Please let me know if you have any concerns/corrections

Thanks in advance

[1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
[2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
[3] https://issues.apache.org/jira/browse/OPENMEETINGS-986

  was:
Hello All,

Due to multiple requests and issues (please see [1], [2], [3]) I would like to change User object (remove status and "user level") and add Permissions.

As I can see the permissions should be
Admin       == access to Admin module
Room        == enter the room
Dashboard == access the whiteboard
Login         == login to Om internal DB
Soap         == use rest/soap calls

for example 
current "regular" user will have all permissions except for Admin and Soap
current "soap" user will have soap permission only
current OAuth user will have no Login parmission

The proposed system looks extendable and should cover all current needs

I'm going to implement it in 3.0.3 and 3.1.0

Please let me know if you have any concerns/corrections

Thanks in advance


> ACLs should be added to the User
> --------------------------------
>
>                 Key: OPENMEETINGS-1017
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1017
>             Project: Openmeetings
>          Issue Type: Improvement
>          Components: Import/Export, Joomla-Plugin, Moodle-Plugin, SOAP/REST API, SugarCRM-Plugin, UI
>    Affects Versions: 3.0.2
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>             Fix For: 3.0.3, 3.1.0
>
>
> Hello All,
> Due to multiple requests and issues (please see [1], [2], [3]) I would like to change User object (remove status and "user level") and add Permissions.
> As I can see the permissions should be
> Admin       == access to Admin module
> Room        == enter the room
> Dashboard == access the whiteboard
> Login         == login to Om internal DB
> Soap         == use rest/soap calls
> for example 
> current "regular" user will have all permissions except for Admin and Soap
> current "soap" user will have soap permission only
> current OAuth user will have no Login parmission
> The proposed system looks extendable and should cover all current needs
> I'm going to implement it in 3.0.3 and 3.1.0
> Please let me know if you have any concerns/corrections
> Thanks in advance
> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986



--
This message was sent by Atlassian JIRA
(v6.2#6252)