-
Type:
Improvement
-
Status: Closed
-
Resolution: Won't Do
-
Affects Version/s: 4.1, 4.2
-
Fix Version/s: None
-
Component/s: Multitenant
-
Labels:None
-
Environment:RHEL, Tomcat, Oracle
-
Bug Priority:
-
ACT Numbers:
00093146,00369021
This relates to ALF-11855
Summary:
http://wiki.alfresco.com/wiki/Multi-Tenancy#Tenant_Customisation, indicates the usage of dynamic models for multitenant environments.
The deployment of the web-client-config-custom.xml can be dynamically deployed as well (http://wiki.alfresco.com/wiki/Dynamic_Models#Deploying_web_client_customisations) but this documentation does not cover the case of share UI which would use "shared-config-custom.xml".
The comment "reloadable Share config (if using dynamic models)" listed here:
http://wiki.alfresco.com/wiki/Multi-Tenancy#Not_Implemented, indicates dynamic deployment for MT is not implemented.
Only option suggested for controlling specific to Tenant MT visibility of aspects/types/actions is "since multiple Share instances can be configured against the same repository, is to have separate Share instances with their own share-config-custom configuration pointing to the same MT Alfresco instance."
Can this be modified so that visibility of types,aspects,properties are tenant specific in share? without having to do a separate install of share for each tenant to accomplish this?
- is related to by
-
MNT-7420 Multitenant: how do you control the visibility of aspects/types/metadata/actions specific only to that tenant in Share UI, using dynamic model/deployment
- Closed