Hi I did a round of testing with the fix and its working fine for us. Thanks & Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729
On Wed, Jun 4, 2014 at 1:59 PM, Danushka Fernando <[email protected]> wrote: > Hi Anjana > Will test with this and reply. Thanks for the quick response. > > Thanks & Regards > Danushka Fernando > Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > > > On Wed, Jun 4, 2014 at 1:22 PM, Anjana Fernando <[email protected]> wrote: > >> Hi guys, >> >> I've attached a patch in the JIRA issue created to fix the issue. It was >> simply removing the full code segment that was creating this behavior, I've >> done some tests after the change, and all seems to be working. Do a round >> of testing for your scenario too to verify the fix and commit the changes. >> >> Cheers, >> Anjana. >> >> >> On Tue, Jun 3, 2014 at 6:08 PM, Danushka Fernando <[email protected]> >> wrote: >> >>> Created [1] >>> >>> [1] https://wso2.org/jira/browse/DS-905 >>> >>> Thanks & Regards >>> Danushka Fernando >>> Software Engineer >>> WSO2 inc. http://wso2.com/ >>> Mobile : +94716332729 >>> >>> >>> On Tue, Jun 3, 2014 at 6:06 PM, Sameera Jayasoma <[email protected]> >>> wrote: >>> >>>> This was written assuming that the DBDeployer will always run in the >>>> super tenant. Danushka, Can you create a Jira to track this? >>>> >>>> Thanks, >>>> Sameera. >>>> >>>> >>>> On Tue, Jun 3, 2014 at 6:05 PM, Anjana Fernando <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> Yeah, seems like a bug, I also can't remember why we are doing this. >>>>> @Prabath, do you remember why we have done such a change there? .. and >>>>> @Chanika, please look into this, and fix for the next release. >>>>> >>>>> Cheers, >>>>> Anjana. >>>>> >>>>> >>>>> On Tue, Jun 3, 2014 at 5:58 PM, Danushka Fernando <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi all >>>>>> I came across following issue recently. Always first call done to AS >>>>>> (As a tenant when tenant is not loaded yet) it fails with access denied. >>>>>> The reason was in authorization handler when we retrieve user realm from >>>>>> carbon context, its not tenant's realm it's super tenant realm. >>>>>> >>>>>> When I was debugging further I found that DBDeployer [1] is setting >>>>>> the wrong user realm to carbon context replacing the correct one set by >>>>>> Carbon Authentication Util. >>>>>> >>>>>> Is there a specific reason for this. Can we fix this to set the >>>>>> correct values ? >>>>>> >>>>>> [1] >>>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/data-services/org.wso2.carbon.dataservices.core/4.2.1/src/main/java/org/wso2/carbon/dataservices/core/DBDeployer.java >>>>>> >>>>>> Thanks & Regards >>>>>> Danushka Fernando >>>>>> Software Engineer >>>>>> WSO2 inc. http://wso2.com/ >>>>>> Mobile : +94716332729 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Anjana Fernando* >>>>> Senior Technical Lead >>>>> WSO2 Inc. | http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> Sameera Jayasoma, >>>> Software Architect, >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: [email protected] >>>> blog: http://sameera.adahas.org >>>> twitter: https://twitter.com/sameerajayasoma >>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>> Mobile: 0094776364456 >>>> >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >> >> >> -- >> *Anjana Fernando* >> Senior Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
