Allow ability to turn off automatic "promotion" to provided user
Description
Environment
Test Plan
Attachments
is related to
Activity

Matthew Jones June 24, 2011 at 7:24 PM
FYI: I believe the scenario you describe is not possible to do anymore because of where this roster removal is blocked. Sounds related.

John Bush June 24, 2011 at 3:49 PM
If you don't turn off automatic promotion, and follow this procedure, experience is bad. This isn't just an edge case to me, seems like a bigger problem, surprised no one else has run into this.
create a site as an instructor, then remove the roster from the site. The instructor is removed from the site and gets "Site Unavaiable". So if say you create a site, realize you picked the wrong roster, then deleted the the roster before adding a new, suddenly you loose access to your site. That would really suck if say you had put a bunch of content in the site already.
Stephen Marquard May 20, 2010 at 3:36 AM
Applied in r77620, thanks for the patch.

BrandenB May 19, 2010 at 7:10 AMEdited
If this patch is applied with no change to sakai.properties, then no current functionality changes.
If you configure:
promoteUsersToProvided@org.sakaiproject.authz.api.AuthzGroupService=false
into sakai.properties, then functionality will return to how it was before .
Stephen Marquard May 19, 2010 at 1:56 AM
As it's a somewhat actual case, I think the bean-value property is probably most consistent with previous practice, e.g. a name/value property in kernel-component/src/main/webapp/WEB-INF/authz-components.xml and settable in sakai.properties as
promoteUsersToProvided@org.sakaiproject.authz.api.AuthzGroupService=true
or similar.
For the edge case where automatic promotion to "provided" users is not desired (), it might be worth being able to toggle this functionality.
More info is on Nabble:
http://n2.nabble.com/Building-Sakai-KNL-403-td5041794.html