[
https://issues.apache.org/jira/browse/OFBIZ-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taher Alkhateeb updated OFBIZ-9278:
-----------------------------------
Attachment: OFBIZ-9278.patch
Okay, I think maybe we caught the problem now. It was hidden in the bowels of the data loading logic which took some time to dig out. Essentially, we need to define readers=tenant when loading the tenant information into the master tenants database.
I think this patch might fix it. Can you please check and confirm?
> Login after multitenant
> -----------------------
>
> Key: OFBIZ-9278
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9278> Project: OFBiz
> Issue Type: Bug
> Affects Versions: Release Branch 16.11
> Environment: linux mint 17.1, MySql 5.5.54
> Reporter: Guillaume Fortin
> Priority: Minor
> Labels: multitenancy, multitenant
> Attachments: OFBIZ-9278.patch, OFBIZ-9278.patch
>
>
> I want to create two tenants named respectively e3 and psp. To create
> them, I use those command lines:
> ./gradlew createTenant -PtenantId=PSP -PtenantReaders=seed,seed-initial
> -PdbPlatform=M -PdbUser=XXXX -PdbPassword=XXXX
> ./gradlew createTenant -PtenantId=E3 -PtenantReaders=seed,seed-initial
> -PdbPlatform=M -PdbUser=XXXX -PdbPassword=XXXXX
> After creating the first tenant, I was able to connect with psp-admin
> user. After I created the second one, I was able to connect to the second
> database e3 with the e3-admin user but impossible to connect again on the
> PSP application.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
