Thanks for the detailed report!
build #27 should address first issue

second was not reproducible here, could you please re-check?


On 13 June 2014 19:33, Michael Wuttke <michael.wut...@beuth-hochschule.de>
wrote:

> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) now with a clean postgresql
> install. Two issues occurred during this test.
>
> 1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7 and
> om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
> like I tested yesterday. But to open the new created OM room via moodle
> doesn't work. In the openmeetings.log file I found the following error
> messages:
> http://pastebin.com/rpTfhJcW
>
> 2. When I tried to add the new soap user to a organisation via the OM
> GUI: Administration -> Usergroups -> selecting the usergroup -> Add user
> via the drop down menu If got an Internal error.
>
> In the openmeetings.log file I found the following error messages:
> http://pastebin.com/q0h1aR3G
>
> Thanks,
> Michael
>
> Am 12.06.2014 20:30, schrieb Maxim Solodovnik:
> > should be fixed
> > Committed revision 1602257.
> >
> > will create another build later this week
> >
> >
> > On 13 June 2014 01:08, Maxim Solodovnik <solomax...@gmail.com
> > <mailto:solomax...@gmail.com>> wrote:
> >
> >     ups :( forgot to check it
> >     will do
> >
> >
> >     On 13 June 2014 01:08, Michael Wuttke <mwut...@beuth-hochschule.de
> >     <mailto:mwut...@beuth-hochschule.de>> wrote:
> >
> >         Hello Maxim,
> >
> >         I've tested the branch 3.0.3 (build 26) with a clean mysql
> install.
> >         The Admin user has now the admin rights. Also the logout is
> possible
> >         now. Adding a 'SOAP' user to create OM rooms via moodle is now
> >         possible.
> >         But the Network testing still doesn't work: Access denied.
> >
> >         Thanks,
> >         Michael
> >
> >         Am 12.06.14 10:09, schrieb Maxim Solodovnik:
> >         > should be fixed
> >         > please try build #26
> >         >
> >         >
> >         > On 11 June 2014 16:14, Maxim Solodovnik <solomax...@gmail.com
> >         <mailto:solomax...@gmail.com>> wrote:
> >         >
> >         >> Thanks!
> >         >> really appreciate your testing efforts :)
> >         >> Will try to fix it ASAP
> >         >>
> >         >>
> >         >> On 11 June 2014 16:09, Juan Carrera <carre...@unizar.es
> >         <mailto:carre...@unizar.es>> wrote:
> >         >>
> >         >>>  Hi, i.ve <http://i.ve> tested on a clean mysql install
> >         (branch 3.0.x)
> >         >>> Admin user has no admin rights, only 'Room', 'Login' and
> >         'Dashboard'.
> >         >>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in
> >         om_user_right
> >         >>> table doesn't work.
> >         >>> Network testing doesn't work for me /Access denied).
> >         >>>
> >         >>>
> >         >>>
> >         >>> El 10/06/14 18:58, Maxim Solodovnik escribió:
> >         >>>
> >         >>> Can you please check if the implemented solution works as
> >         expected?
> >         >>> Latest 3.0.3 build contains the changes
> >         >>>
> >         >>>
> >         >>> On 2 June 2014 17:31, Michael Wuttke
> >         <michael.wut...@beuth-hochschule.de
> >         <mailto:michael.wut...@beuth-hochschule.de>>
> >         >>> wrote:
> >         >>>
> >         >>>> Hello Maxim,
> >         >>>>
> >         >>>> I think so too, using OM via moodle or directly via LDAP
> >         like Juan in
> >         >>>> the jira issue nr. 1007 described - with the same
> >         credentials would be
> >         >>>> great.
> >         >>>>
> >         >>>> Thanks & Greetings,
> >         >>>> Michael
> >         >>>>
> >         >>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> >         >>>>  > 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
> >         >>>>>
> >         >>>>> --
> >         >>>>> WBR
> >         >>>>> Maxim aka solomax
> >         >>>>
> >         >>>
> >         >>>
> >         >>>
> >         >>>  --
> >         >>> WBR
> >         >>> Maxim aka solomax
> >         >>>
> >         >>>
> >         >>> --
> >         >>>   [image: Logotipo del servicio de informática y
> comunicaciones.
> >         >>> Universidad Zaragoza]
> >         >>>
> >         >>> *Juan Ramón Carrera Marcén *
> >         >>> * Área de gestión*
> >         >>> Residencia de profesores
> >         >>> Pedro Cerbuna 12, 50009 Zaragoza
> >         >>> Tel. (34) 876553689
> >         >>> carre...@unizar.es <mailto:carre...@unizar.es>
> >         >>>
> >         >>> [image: unizar.es <http://unizar.es>]
> >         >>>
>
>


-- 
WBR
Maxim aka solomax

Reply via email to