[OFBIZ-6061] 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.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 12.04.04, 12.04.05, 13.07.01, Trunk
• Fix Version/s: Release Branch 11.04, Release Branch 12.04, Release Branch 13.07, Trunk
• Component/s: framework
• Labels: login multi-tenant
• Assignee: Gavin Mabie
• Reporter: Gavin Mabie
• Created: 06/Feb/15 10:49
• Updated: 10/Apr/15 15:29
• Resolved: 10/Feb/15 04:18

Description

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.

Issue Links

• relates to: OFBIZ-5986 Error on accessing new tenant
• relates to: OFBIZ-5898 Tenant should run with specified domain name. Front store should support multi tenant feature.