Ok digging down deeper.
svn583354
note: I am focusing on the userlogin
I have validated that the loginID is in the GenericValue userLogin
next
                productinfo.put("userLogin", userlogin);
plus all the rest of the stuff.
            dispatcher.runSyncIgnore("createProduct", productinfo);
I get down to servicedispatcher.java (line 758)
            // if a userLogin object is there, make sure the given
username/password exists in our local database
            GenericValue userLogin = (GenericValue)
//added to verify userlogin.
context.get("userLogin");
                        Debug.logInfo("userLogin="
                                        + userLogin.getString("userLoginId"), 
module);

error:
Service [createProduct] threw an unexpected exception/error
Exception: java.lang.NullPointerException
Message: null
---- stack trace
---------------------------------------------------------------
java.lang.NullPointerException
org.ofbiz.service.ServiceDispatcher.checkAuth(ServiceDispatcher.java:756)

so if I have it down right my userlogin is not getting passed down.
if there is another place I can put a debug to check were in the stream
it is losing it let me know.
it would cut my debug time.


BJ Freeman sent the following on 10/9/2007 5:27 AM:
> this is a automatic process
> I am reading a remote xml of products from site
> I am then updating the catalogs for that site in ofbiz.
> since on user interaction is done thought system would be a good one to use
> Since then I have created a party group and put a login that is a system
> login.
> still does not work.
> 
> Scott Gray sent the following on 10/8/2007 10:41 PM:
>> Why do you want the system login to create a product?  Isn't that something
>> a user with the correct permissions would normally do?
>>
>> Regards
>> Scott
>>
>> On 09/10/2007, BJ Freeman <[EMAIL PROTECTED]> wrote:
>>> Claification
>>>
>>> https://localhost:8443/webtools/control/availableServices?sel_service_name=createProduct
>>> so no security
>>> yet
>>> org/ofbiz/product/product/ProductServices.xml
>>> shows
>>>         <check-permission permission="CATALOG" action="_CREATE">
>>>             <alt-permission permission="CATALOG_ROLE" action="_CREATE"/>
>>>             <fail-message message="Security Error: to run createProduct
>>> you must have the CATALOG_CREATE or CATALOG_ADMIN permission, or the
>>> limited CATALOG_ROLE_CREATE permission"/>
>>>         </check-permission>
>>> so why does this not show up in the services page for createProduct
>>> is there a bug in the process that read the simple services and not
>>> catch the security?
>>>
>>> could that bug also be causing my problem?
>>>
>>> BJ Freeman sent the following on 10/8/2007 12:02 AM:
>>>> Ok I have dug down into the serviceDipatcher.java and  Modelservice.java
>>> .
>>>> and I am lost.
>>>> I looked at the permissions for createprodcut and I have them on the
>>>> login that i am passing down.
>>>> secturity groups
>>>> CATALOG_ADMIN
>>>> CATALOGADMIN
>>>> CATALOG_ADMIN_LTD This is the one in createproducts service.
>>>> AND
>>>> FULLADMIN for good messure
>>>>
>>>> since I don't see createproduct being used can some one look at it as
>>>> see if it is the way it is suppose to be.
>>>>
>>>> save me some time tracking it down.
>>>>
>>>> BJ Freeman sent the following on 10/7/2007 12:17 PM:
>>>>> do a custom createproduct
>>>>> getting this message
>>>>> Service [createProduct] threw an unexpected exception/error
>>>>> Exception: org.ofbiz.service.ServiceAuthException
>>>>> Message: User authorization is required for this service: createProduct
>>>>> I login via
>>>>>                      userLogin = delegator.findByPrimaryKey("UserLogin",
>>> UtilMisc
>>>>>                                      .toMap("userLoginId", "system"));
>>>>> and passing that in for the login.
>>>>>
>>>>> My question is, do I have to explicity add the system login to the
>>>>> createproduct service or add the permissions in the createproduct
>>>>> service to the system login?
>>>>> I believe the latter is the correct way to go.
>>>>>
>>>>>
>>>>>
>>>>
> 
> 
> 

Reply via email to