[sakai2-tcc] Sakai support for better OOTB integration with uPortal

Matthew Jones matthew at longsight.com
Fri Sep 27 07:44:37 PDT 2013


I don't think we should add anything else new by default. If you want to
add new stuff (users or sites) to the demo provider or demo startup that's
fine with me though. All QA and test instances start up using the demo
property.

I think it would be better if mercury site was created by this demo class
too rather than the sql scripts, and I personally rarely use the mercury
site, so the only thing that happened OOTB was the admin user creation.
This just isn't cleanup that ever happened.



On Fri, Sep 27, 2013 at 2:59 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Hello
>
> The Sakai Connector Portlet has passed the Jasig/Apereo incubation process
> and is in the midst of being incorporated into the next uPortal release.
>
> This portlet uses the trusted mode of the Basic LTI support in Sakai to
> allow a user with the same username in both systems to embed tools from
> their Sakai sites inside uPortal.
>
> Sakai currently has LTI configuration in the experimental sakai props to
> support this, ie the demo of uPortal hooks up to the Sakai experimental
> server.
>
> It so happens that uPortal ships with an admin user so for that user the
> OOTB experience works fine. However uPortal also ships with two other demo
> users called student and faculty. These have no equivalent in Sakai so the
> demo does not work for those users. These users are important in
> demonstrating the various layouts and portlet that uPortal offers.
>
> What I propose is that these two users are added to Sakai by default. The
> student would be an access user in mercury, the faculty would be a maintain
> user.
>
> This also ties in with my earlier emails of providing a better OOTB
> experience for Sakai.
>
> Please reply with any comments or concerns. I would like to get this in as
> soon as I can if there are no objections.
>
> Regards
> Steve
>
> Ps. I sent this to the sakai-pmc at collab.sakaiproject.org list but it
> bounced because I wasn't subscribed. I presume others aren't yet either so
> am sending to the tcc list.
>
> sent from mobile device
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130927/85a6220a/attachment.html 


More information about the sakai2-tcc mailing list