Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. 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.

    XMLWordPrintableJSON

    Details

      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.

        Attachments

        1. MultiTenantLoginWorker.patch
          2 kB
          Gavin Mabie

          Issue Links

            Activity

              People

              • Assignee:
                gavin.mabie@urbannex.co.za Gavin Mabie
                Reporter:
                gavin.mabie@urbannex.co.za Gavin Mabie
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: