At this week's developer meeting, there was discussion around multi tenancy and 
the problems that people are running into with this feature. The consensus was 
to switch multi tenancy off by default, a change I have implemented and 
submitted yesterday [MH-8446].

In order to take advantage of the zero-configuration approach in terms of multi 
tenancy you need to make sure that there is *only one* organization file in 
your /load directory. By default, this will be the file 

org.opencastproject.organization-mh_default_org.cfg

On existing installations, there my also be a second sample configuration

org.opencastproject.organization-tenant1.cfg

which should be removed. The change basically makes sure that as long as there 
is only one configuration, it is being used as the default organization, no 
matter what the url is that is used to access the system. As soon as you add a 
second tenant configuration, rules are as they have been so far: the 
organization will be mapped by looking at the url that is used to access the 
system. If no organization definition can be found with that url, the request 
will be rejected.

Tobias

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to