Hi Nuwan, The requirement is that the EntitlementFilter is already implemented in the identity.entitlement.filter component. So its s simply matter of adding it into the web application. Since Jaggery does not have filters either we should proceed with WS/REST api as you suggest or implement filters in Jaggery. Implementing the filter in Jaggery is simple since its only matter of registering filters like you do for websockets (though it needs to be carefully designed to handle filter chains).
"There are no filters in jaggery world" Does this mean it will not be supported at all in the future or is it wrong architecture wise to implement such? "route all requests through one controller which will act as your filter" Will this actually behave as a filter? I believe this should stand infront of the Jaggery front controller servlet hence it should also go as a filter without filtering after it received by looking at its content or any other property. WDYT? Please suggest the best approach. Regards, Dilshan On Wed, Jul 10, 2013 at 12:43 PM, Nuwan Bandara <[email protected]> wrote: > > > > On Wed, Jul 10, 2013 at 12:33 PM, Gayan Gunawardana <[email protected]>wrote: > >> Hi Nuwan, >> >> Yes, WSO2 IS is the PDP but it's more easy to invoke Entitlement Service >> through EntitlementFilter than direct WS/REST calls. >> > > There are no filters in jaggery world, what you can do is, route all > requests through one controller which will act as your filter > > Regards, > /Nuwan > > >> >> >> On Wed, Jul 10, 2013 at 12:14 PM, Nuwan Bandara <[email protected]> wrote: >> >>> Hi Gayan, >>> >>> XACML engine is a policy evaluation module. You dont need a special type >>> of binding for that. What you can do is, forward the attributes you want to >>> evaluate against a XACML policy to the XACML engine via a REST call or a WS >>> call. >>> >>> for instance, WSO2 IS can be the XACML PDP, where your jaggery >>> application will be the PEP. so you can call IS via WS/REST with the >>> attributes and get the result which is given by the IS as the response. >>> >>> Regards, >>> /Nuwan >>> >>> >>> On Wed, Jul 10, 2013 at 12:07 PM, Gayan Gunawardana <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> For MDM we have a requirement to bind with XACML engine inside a >>>> jaggery application. >>>> >>>> org.wso2_.carbon.identity.entitlement.filter_0.zip available in >>>> application server but jaggery does not support custom filters. >>>> >>>> Is it allow to add custom filters to jaggery-core or is there any other >>>> option. >>>> >>>> >>>> -- >>>> Gayan Gunawardana >>>> Software Engineer; WSO2mobile Inc.; http://wso2mobile.com/ >>>> Email: [email protected] >>>> Mobile: +94 (71) 8020933 >>>> Blog: http://gayanj2ee.blogspot.com/ >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://mail.jaggeryjs.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Thanks & Regards, >>> >>> Nuwan Bandara >>> Technical Lead; **WSO2 Inc. * >>> *lean . enterprise . middleware | http://wso2.com * >>> *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >>> 9629 >>> * >>> <http://www.nuwanbando.com/> >>> >> >> >> >> -- >> Gayan Gunawardana >> Software Engineer; WSO2mobile Inc.; http://wso2mobile.com/ >> Email: [email protected] >> Mobile: +94 (71) 8020933 >> Blog: http://gayanj2ee.blogspot.com/ >> > > > > -- > *Thanks & Regards, > > Nuwan Bandara > Technical Lead; **WSO2 Inc. * > *lean . enterprise . middleware | http://wso2.com * > *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > > _______________________________________________ > Dev mailing list > [email protected] > http://mail.jaggeryjs.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
