[Building Sakai] Sections
Nguni Phakela
nguni52 at gmail.com
Fri Oct 12 01:12:46 PDT 2012
Hi All,
I found a solution.
Although the realms are set at a high level, the problem is for each new
group that has been creted, realm.upd.own is not checked.
This means that for each new section that is created manually, for students
to join, each group in realms needs the realm.upd.own to be checked.
I would think that these realm permissions are inherited.
Cheers,
Nguni
On Thu, Oct 11, 2012 at 4:44 PM, Nguni Phakela <nguni52 at gmail.com> wrote:
> Hi,
>
> This is the exception I'm getting when trying to add a student to the
> course so I have ticked the checkbox for this realm in that particular site.
>
> I'm still receiving the exception
>
> org.sakaiproject.component.section.sakai.SectionManagerImpl - access
> denied while attempting to join authz group:
> org.sakaiproject.authz.api.AuthzPermissionException
> user=d4625e55-d0b5-4a49-ae86-87c4e4c1d1b9 function=realm.upd.own
> resource=/site/MATH1014_ADU/group/8ce06edf-612a-4e09-a645-9ae73f70aac5
> at
> org.sakaiproject.authz.impl.BaseAuthzGroupService.unlock(BaseAuthzGroupService.java:162)
> at
> org.sakaiproject.authz.impl.BaseAuthzGroupService.joinGroup(BaseAuthzGroupService.java:391)
> at
> org.sakaiproject.component.section.sakai.SectionManagerImpl.joinSection(SectionManagerImpl.java:701)
> at
> org.sakaiproject.component.section.sakai.SectionManagerImpl.joinSection(SectionManagerImpl.java:690)
> at
> org.sakaiproject.tool.section.jsf.backingbean.StudentViewBean.processJoinSection(StudentViewBean.java:201)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:132)
> at javax.faces.component.UICommand.broadcast(UICommand.java:89)
> at javax.faces.component.UIData.broadcast(UIData.java:517)
> at
> javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:97)
> at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:171)
> at
> org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:32)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:95)
> at
> org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.sakaiproject.util.RequestFilter.doFilter(RequestFilter.java:598)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at
> org.sakaiproject.tool.section.filter.RoleFilter.doFilter(RoleFilter.java:129)
>
>
>
>
> On Thu, Oct 11, 2012 at 4:16 PM, Nguni Phakela <nguni52 at gmail.com> wrote:
>
>> Hi Mariano,
>>
>> We don't have a setup like that. Only the first part of your
>> configuration is similar to ours:
>>
>> ROLE: Student
>>
>> REALM: site.template
>> group.template
>> PERMISSION: section.role.student
>> section.role.student
>>
>> The one that shows that this is related to permissions though is the fact
>> that a student cannot join, but when an instructor assigns them to a
>> section, then they are enrolled in that section.
>>
>> Cheers,
>> Nguni
>>
>>
>> On Thu, Oct 11, 2012 at 1:00 PM, JOSE MARIANO LUJAN GONZALEZ <
>> jmariano at um.es> wrote:
>>
>>> uhmmm...
>>> and have you checked the permissions in the group template. In the same
>>> site, in the group.template, you cant have two roles with the permission
>>> section.role.student. That was my second guess, i dont remember the error
>>> message that when we first configured our permissions but we did have
>>> problems with those permissions.
>>>
>>> i.e. with three tipe of students:
>>>
>>> GOOD CONFIGURATION
>>>
>>> ROLE: Student
>>>
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student
>>> section.role.student
>>>
>>> ROLE: GuestStudent
>>>
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student --
>>>
>>> ROLE: ExternalStudent
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student --
>>>
>>> WRONG CONFIGURATION
>>>
>>> ROLE: Student
>>>
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student
>>> section.role.student
>>>
>>> ROLE: GuestStudent
>>>
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student
>>> section.role.student
>>>
>>> ROLE: ExternalStudent
>>> REALM: site.template
>>> group.template
>>> PERMISSION: section.role.student
>>> section.role.student
>>>
>>>
>>> We actually had this problems with our teachers since we created 4
>>> different roles that all of them acted like an instructor so we gave
>>> section.role.instructor to all 4 roles in group.template and that caused a
>>> problem. Not sure if its the same that one that you have.
>>>
>>> mariano
>>>
>>>
>>> El 11/10/2012 12:47, Nguni Phakela escribió:
>>>
>>> Hi Mariano,
>>>
>>> There are lecturer Sections, and then Tutorial Sections. They are
>>> already part of Lecture Sections, but now there are new sections that have
>>> been created, of the category Tutorial.
>>>
>>> They surely should not have any conflicts.
>>>
>>> Nguni
>>>
>>> On Thu, Oct 11, 2012 at 12:24 PM, JOSE MARIANO LUJAN GONZALEZ <
>>> jmariano at um.es> wrote:
>>>
>>>> Hi Nguni,
>>>> Are you using the tool Section Info? If you do, you should have in mind
>>>> that Sections are designed to work with categories.
>>>>
>>>> In your case, if a Teacher creates a two sections (SECTION A and
>>>> SECTION B - both from the same category i.e. 'lab') then a student will
>>>> only be able to join one of those two sections.
>>>>
>>>> From the Official Sakai Guide Book: "Unlike groups, a student can
>>>> belong to only one section of a given type at a time. For example, it does
>>>> not make sense for a student to be in tow labs in the same course." So your
>>>> error might come from there and that is why the concept of "category" was
>>>> introduced.
>>>>
>>>> or
>>>>
>>>> We also had some problems at the beginning when customizing our own
>>>> roles and permissions. You should check your realms in that site and check
>>>> for the "section.role.instructor, section.role.ta and section.role.student"
>>>> permissions to check if they have been configured properly. I recomend you
>>>> to take a deeper look into this confluence page:
>>>> https://confluence.sakaiproject.org/display/SECT/Authorization+and+Section+Awareness+rules+in+Sakai+2.1
>>>>
>>>> *The SectionAwareness API uses the following rules when determining
>>>> the membership lists of sites and sections
>>>> *
>>>>
>>>> Hope that helps!
>>>> mariano
>>>>
>>>>
>>>>
>>>> El 11/10/2012 11:38, Nguni Phakela escribió:
>>>>
>>>> Hi All,
>>>>
>>>> We have a scenario: When creating a course, students are
>>>> automatically added to rosters based on university slots/sections.
>>>>
>>>> Now, a Lecturer wants to create sections for different groups for
>>>> tutorial sections.
>>>>
>>>> So they go to options and click on the options for manually managing
>>>> sections and students being able to select which tutorial
>>>> section they want to be a part of.
>>>>
>>>> They are able to create these sections: However, when a student click
>>>> on the link Join, they get this error:
>>>>
>>>> You are already a member of a section in this category.
>>>>
>>>> Would anyone know the cause of this and how to resolve it.
>>>>
>>>> Cheers
>>>>
>>>> --
>>>> Nguni Phakela
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>
>>>>
>>>> --
>>>> ******************************************
>>>> José Mariano Luján González - Aula Virtual
>>>> Area de Tecnologías de la Información
>>>> y las Comunicaciones Aplicadas (ATICA)
>>>> UNIVERSIDAD DE MURCIA - http://www.um.es
>>>>
>>>>
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to
>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>> "unsubscribe"
>>>>
>>>
>>>
>>>
>>> --
>>> Nguni Phakela
>>>
>>>
>>> --
>>> ******************************************
>>> José Mariano Luján González - Aula Virtual
>>> Area de Tecnologías de la Información
>>> y las Comunicaciones Aplicadas (ATICA)
>>> UNIVERSIDAD DE MURCIA - http://www.um.es
>>>
>>>
>>
>>
>> --
>> Nguni Phakela
>>
>>
>
>
> --
> Nguni Phakela
>
>
--
Nguni Phakela
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121012/cafb2662/attachment.html
More information about the sakai-dev
mailing list