[Building Sakai] Displaying Course Tool only to Administrators in Sakai

[Steve Swinsburg]

There is, but there is no way for the *portal* to know that a tool is only to be rendered for super users.

A tool can easily use that API and present an alternate UI to a user that is not allowed to view that tool, but the tools will still show up in the list. The original post was about how to completely disable a tool from showing in the portal unless you are admin. 

cheers,
Steve



On 12/04/2011, at 12:37 AM, Earle Nietzel wrote:

> There is this api in the kernel.
> 
>     /**
>      * Is this a super special super (admin) user?
>      * 
>      * @return true, if the user is a cut above the rest, false if a mere mortal.
>      */
>     boolean isSuperUser();
> 
>     /**
>      * Is this user a super special super (admin) user?
>      * 
>      * @param userId
>      *        The user to test.
>      * @return true, if this user is a cut above the rest, false if a mere mortal.
>      */
>     boolean isSuperUser(String userId);
> 
> Earle
> 
> On Sat, Apr 9, 2011 at 7:22 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> I think the issue here might be that roles can be customised per site, and many tools actually allow this customisation to occur within the site, so role_1 in site_a might not necessarily be the same as role_2 in site_b.
> 
> Maybe we need some more permissions that identify admin people.
> 
> cheers,
> Steve
> 
> 
> On 09/04/2011, at 5:17 AM, Zhen Qian wrote:
> 
>> Seth:
>> 
>> I think the transition from role.required to function.required is actually documented inside SAK-4120 that Kara referred to: 
>> 
>> Nuno originally proposed the ticket for "roles.allow" and "roles.deny" configuration. However, Chuck eventually implemented it based on permission: 
>> 
>> "This solution is different than proposed in the patches because it is based on Sakai security functions rather than roles. The patches also proposed an allow/deny pattern. The use of functions instead of roles aligns much better with the Sakai security model and does not require the allow/deny."
>> 
>> Thanks,
>> - Zhen
>> 
>> On Fri, Apr 8, 2011 at 2:23 PM, Seth Theriault <slt at columbia.edu> wrote:
>> Zhen Qian wrote:
>> 
>> Maybe besides function, we can request a feature to restrict tool display based on roles, e.g. role.require?
>> 
>> I distinctly remember this coming up a few years back. It's a hazy memory, but I think that approach may have been abandoned in favor on the current "functions.require" one.
>> 
>> Of course, I haven't found  the corresponding Jira. Yet.
>> 
>> Seth
>> 
>> 
>> _______________________________________________
>> 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"
> 
> 
> _______________________________________________
> 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"
> 
> _______________________________________________
> 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"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110412/6c5678da/attachment.html