Hi all,
could you have a look at the attached simple patch? It fixes an
authorization problem under some special situations (switching from
anonymous user to authenticated one...); however the issue is that, when
the "createUserLogin" is called, if the attribute include-user-login is
not set to false the manually passed in "system" user is overwritten by
the user in the context.
Should I commit this patch?
Or, in general, would be better, even if include-user-login is true, to
set the user login only if one is not already there in the service in map?
Jacopo
Index: applications/party/script/org/ofbiz/party/party/PartySimpleMethods.xml
===================================================================
--- applications/party/script/org/ofbiz/party/party/PartySimpleMethods.xml
(revisione 499802)
+++ applications/party/script/org/ofbiz/party/party/PartySimpleMethods.xml
(copia locale)
@@ -85,7 +85,7 @@
<field-map field-name="userLoginId" value="system"/>
</entity-one>
- <call-service service-name="createUserLogin"
in-map-name="createUlInMap"/>
+ <call-service service-name="createUserLogin"
in-map-name="createUlInMap" include-user-login="false"/>
<entity-one entity-name="UserLogin" value-name="newUserLogin"/>
<field-to-result field-name="newUserLogin"/>
