[
https://issues.apache.org/jira/browse/OFBIZ-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940409#comment-13940409 ]
Pierre Smits commented on OFBIZ-5585:
-------------------------------------
Wai,
With functionalities in current feature set we use the context parameter <param-name>entityDelegatorName</param-name> in web.xml of bespoke components/applications to have an assurance that we:
* these bespoke components/applications are only accessible for user of that tenant c.q. delegator,
* comply with respect to NDA's with our customers,
so that we can avoid accidental misconfigurations beyond the 'mulitytenant=Y' that could lead to situations we don't want.
Do you, as the creator of the patch, know whether this setting of the context parameter in the web.xml of a component would still work (and deliver the intended effect) when having applied your patch?
Regards,
Pierre
> multitenant supports tenant selection based on server/domain name
> -----------------------------------------------------------------
>
> Key: OFBIZ-5585
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5585> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Reporter: Wai
> Attachments: ofbiz-multitenant.patch
>
>
> A user can now select one or the other in multitenant mode
> 1) Select a tenant by explicitly specifying the tenantId in the login page (previously implemented)
> 2) Assign a domain name to each tenant. Hence, the user does not need to explicitly enter the tenantId. The domain name will automatically select the tenant.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Locked
