We need to fix these blockers related to entitlement mediator, before creating the RC packs that we are planing to release on Tuesday.
Thanks, On Thu, Jan 23, 2014 at 10:23 AM, Shashika Ubhayaratne <shash...@wso2.com>wrote: > Hi Asela, > > Please fix issue [1] as well since it is a blocker for ESB. Throws null > pointer for thrift requests on IS 4.6.0. > > [1]: https://wso2.org/jira/browse/IDENTITY-2000 > > Thanks, > Shashika > > > Shashika Ubhayaratne > Associate Technical Lead - QA > WSO2 Inc: http://www.wso2.com/ > Mobile: *+94773383831* > > > On Thu, Jan 23, 2014 at 7:37 AM, Asela Pathberiya <as...@wso2.com> wrote: > >> >> >> >> On Wed, Jan 22, 2014 at 7:45 PM, Dushan Abeyruwan <dus...@wso2.com>wrote: >> >>> Hi IS Team, >>> ESB 4.8.1 M1 pack built today with IS 4.6.0 (released) >>> >>> This is reproducible, seems like now response wrap >>> with urn:oasis:names:tc:xacml:3.0:core:schema:wd-17 and no longer >>> >>> if(decisionString != null){ >>> OMElement decisionElement = >>> AXIOMUtil.stringToOM(decisionString); >>> * simpleDecision = >>> decisionElement.getFirstChildWithName(new >>> QName("Result")).getFirstChildWithName(new QName("Decision")).getText();* >>> obligations = decisionElement.getFirstChildWithName(new >>> QName("Obligations")); >>> advice = decisionElement.getFirstChildWithName(new >>> QName("AdviceExpressions")); >>> if(log.isDebugEnabled()){ >>> log.debug("Entitlement Decision is : " + >>> simpleDecision); >>> } >>> >>> it suppose to be >>> >>> *decisionElement.getFirstChildWithName(new >>> QName("urn:oasis:names:tc:xacml:3.0:core:schema:wd-17","Result")) or may be >>> we might have to test both..* >>> >>> So, IS team please review this and do any necessary changers to >>> Entitlement Mediator, this a BLOCKER and required your attention. >>> >>> New Response Type.. >>> <Response >>> xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17"><Result><Decision>NotApplicable</Decision><Status><StatusCode >>> Value="urn:oasis:names:tc:xacml:1.0:status:ok"></StatusCode></Status></Result></Response> >>> >> >> >> Yes.. Thanks for pointing out. We need to fix the entitlement mediator >> for 4.8.0. Because XACML 3.0 response must return with above namespace and >> entitlement mediator always sends a XACML 3.0 request. Actually namespace >> was fixed in 4.6.0 IS release [1], Therefore we can consider both >> situations; when fixing the entitlement mediator. Then it would work with >> both older and new IS versions. >> >> [1]https://wso2.org/jira/browse/IDENTITY-1855 >> >> Thanks, >> Asela. >> >> >>> >>> Cheers, >>> Dushan Abeyruwan | Associate Tech Lead >>> Integration Technologies Team >>> PMC Member Apache Synpase >>> WSO2 Inc. http://wso2.com/ >>> Blog:http://dushansview.blogspot.com/ >>> Mobile:(0094)713942042 >>> >>> >> >> >> -- >> Thanks & Regards, >> Asela >> >> ATL >> Mobile : +94 777 625 933 >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
