[SAK-13205] Permissions for CIG Participant are empty for 2.5 upgrade Created: 13-Mar-2008 Updated: 13-Jul-2016 Resolved: 20-Mar-2008
|Component/s:||OSP: Portfolios, OSP: Wizards - General, OSP: Wizards - Hierarchy, OSP: Wizards - Matrix, OSP: Wizards - Sequential|
|Fix Version/s:||2.5.2, 2.6.0|
|Reporter:||Lynn E. Ward||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Win XP, IE 7.x, Sakai QA Network qa2-osp (svn tags/sakai_2-5-0_RC_03_GMT) using Oracle
I just created a new account and a new portfolio site on QA2. No permissions are checked for the CIg participant in the matrices, wizards, and portfolio tools.
Note that the QA2 database is created from a 2.4 snapshot, which is then upgraded to 2.5 using conversion scripts. The problem appears to be with upgrade. New sites in an upgrade sakai instance have incorrect/incomplete osp permissions, while existing sites have no permissions at all for many osp tools.
|Comment by Beth Kirschner [ 19-Mar-2008 ]|
Current permissions defaults for new 2.5 worksites:
Role: CIG Coordinator
Role: CIG Participant
Role: Program Admin
Role: Program Coordinator
Role: Teaching Assistant
|Comment by Beth Kirschner [ 20-Mar-2008 ]|
There were a couple problems found: (1) default permissions were not correctly set in an upgrade; (2) older 2.4 permissions were not upgraded to 2.5.
Please merge into 2.5.x
|Comment by David Horwitz [ 27-Mar-2008 ]|
merged into 2-5-x with r43716.
|Comment by Kevin Chan [ 31-Mar-2008 ]|
As a non-OSP user for our Sakai 2.4, I just tried a 2.5.x upgrade deployment and ran into the warnings from updates related to this JIRA:
[This was first brought up by Stephen Marquard on sakai-dev:
WARN: Unable to find user: /site/c8f56c54-23ed-4f87-00c1-6f5d1463cb5e/Student org.sakaiproject.exception.IdUnusedException id=/site/c8f56c54-23ed-4f87-00c1-6f5d1463cb5e (2008-03-28 19:04:28,688 main_org.sakaiproject.metaobj.security.impl.sakai.AgentManager)
Though warnings are generally benign, for some reason, these warnings prevented my Sakai 2.5.x instance from deploying. I had to turn it off in sakai.properties (via osp.upgrade25=false) before the deployment was successful.
So if there is some time, can someone make sure that this upgrade script plays nicely for those installations that did not use OSP prior to Sakai 2.5?
|Comment by Megan May [ 03-Oct-2008 ]|
These fixes have been included in an official foundation release so I am marking them as closed and unassigning them from the Sakai QA account