After adding a little Debug output on the Service Dispatcher it is clear
what's going on:
ServiceDispatcher.getDelegator() returns the default delegator while my
userLogin in context is valid for a tenant delegator, ie. default#MYTENANT
Is this a known issue? Has anyone attempted to adapt the ServiceDispatcher
to use the current user's context delegator? Is there risk bound to it? Or
should I just locally adapt the auth method to use the correct delegator
and keep ServiceDispatcher.delegator with the 'default' ?
I shall go for that latter and play around a bit while waiting for replies
here.
Once solution found, it merit's a JIRA I guess.
Regards
Carsten
2012/8/23 Jacques Le Roux <jacques.le.r...@les7arts.com>
> Adam (doogie) has introduced some changes recently (early may) in this
> area, could be related...
>
> Jacques
>
> From: "Carsten Schinzer" <c.schin...@gmail.com>
>
> Guys, I am still running with this (I can only do that part-time in my
>> evenings). Here is more findings (but still no solution):
>>
>> The error message is legged when in methodContext there is no userId set.
>> Now I wonder how that can happen, as I am logging into the ordermgr
>> application (with permissions set to ORDERMGR_ADMIN), then define a search
>> on the CustRequest search form before I get the error message in the logs
>> when the result list is rendered.
>>
>> Also strange: When I try to change my password I get thrown out from the
>> PartyMgr screen as having no permission.
>>
>> Even more strange: When I attempt to see PartyMgr function from the menu I
>> am prompted to change my password.
>>
>> Finally entirely strange: Checking the encrypted default passwords from
>> the
>> demo data files I see a discrepancy between trunk demo data and 10.04 demo
>> data. Assuming, both string values represent a SHA-hashed "ofbiz" as a
>> password, then why are they different as follows:
>>
>> 10.04 hashed value: currentPassword=
>> "{SHA}**47ca69ebb4bdc9ae0adec130880165**d2cc05db1a"
>> trunk hashed value: currentPassword=
>> "{SHA}**47b56994cbc2b6d10aa1be30f70165**adb305a41a"
>>
>> I admit I am confused. If anyone can shed light into this .... very much
>> appreciated.
>>
>> Did I miss a step when upgrading from 10.04 to trunk recently ?
>>
>> Thanks & regards
>>
>>
>> Carsten
>>
>>
