[
https://issues.apache.org/jira/browse/OFBIZ-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313523#comment-14313523
]
Gavin Mabie commented on OFBIZ-6061:
------------------------------------
Hi Arun
I will close this issue as a duplicate and make further contributions under
OFBIZ-5986. I urge you to take a look at the patch provided here to see how it
can assist with dealing with some of the issues you are still addressing under
5986.
Gavin
> When logging out in a multi-tenant environment, loginWorker strips the
> tenantId from the delegator - reverting to default. This is fine for the
> back-end, but it causes havoc with front-end applications.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-6061
> URL: https://issues.apache.org/jira/browse/OFBIZ-6061
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk, 12.04.04, 12.04.05, 13.07.01
> Reporter: Gavin Mabie
> Assignee: Gavin Mabie
> Priority: Minor
> Labels: login, multi-tenant
> Fix For: Release Branch 11.04, Release Branch 12.04, Release
> Branch 13.07, Trunk
>
> Attachments: MultiTenantLoginWorker.patch
>
>
> 1. When logging out in a multi-tenant environment, users have the ability to
> 2. specify a tenantId when they want to login again;
> 3. This is the result of the doBasicLogout method in LoginWorker.java which
> basically resets the delegator to default when a logout occurs;
> 4. While this works well for back-end multi-tenant applications, it presents
> an issue with tenant-specific applications. The tenant-specific application
> data resides in the tenant db andthis creates problems when the logout resets
> to
> default.
> 5. This proposal utilises the entityDelegatorName as specified in the
> component's web.xml to:
> 5.1 Check if there is a tenant involved, in which case it will use this as
> reset delegator;
> 5.2 If not, it reverts to the default delegator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
