On Mon, Dec 7, 2009 at 10:37 PM, Philippe A. <[email protected]> wrote: > Thanks Sagara. You have answered all there was to answer, even more than I > was hoping. > > I am a bit at the feasability stage. My concern was to find out if Acegi was > meant to be used within a webapp only. I glad to know it isn't. I have also > found in the Acegi documentation that Acegi "will execute in a Java 1.3 > environment" [1].
Acegi designed as a security service for J2EE-based enterprise applications, You may use some of the features of Acegi in a non web application but in a webapp you can get full features of Acegi. > > Another question I have: has anyone published a complete Axis to Acegi > bridge (that is, not limited to username tokens)? I'm referring the bridge > concept in this article [2]. I found it great btw. Rampart is a WS-Security module for Axis2 , in my last post i have provided a reference to show how you can plug Acegi features in to Rampart through the CallbackHandler. I took username tokens only as a one example , you can use same integration concept for other security requirements too. The article you have mentioned is about how you can integrate Axis1 with Acegi by implementing a Axis Handler. If you want you can write a Axis2 Handler and possible to use same design with a Axis2 custom module, this guide [1] will help you to write Axis2 module. This is an another approach to integrate Acegi with Axis2 without using Rampart module. [1] - http://ws.apache.org/axis2/1_5_1/modules.html thanks , > > [1] > http://www.acegisecurity.org/guide/springsecurity.html#runtime-environment > [2] > http://onjava.com/onjava/2006/09/06/separation-of-concerns-in-web-services.html > > 2009/12/5 Sagara Gunathunga <[email protected]> >> >> Yes, there is no in-build integration between Axis2 and Acegi but it >> doesn't imply you can't use Acegi with Axis2 or Rampart. If this >> question related to "sufficient functionality" then the answer is >> "yes". >> >> In case of Axis2, it's again simple as accessing to Spring >> ApplicationContext , once you have access to the ApplicationContext >> you can use Acegi features such as >> AccessDecisionManager , AuthenticationManager etc. In most of the >> cases this is enough to achieve Acegi Authentication/Authorization. >> May be you will find some issues to achieve advanced features of Acegi >> , if so reporting such instances is important to find out possible >> solution too. >> >> But integrating Rampart with Acegi is a bit of a challenging task >> because there is no API method available to access ApplicationContext >> within the Rampart CallbackHandler . But it is possible to find a >> work-around for this depending on your requirements. As a example this >> one [1] worked with me for two of my past applications. >> >> [1] - >> http://ssagara.blogspot.com/2009/05/acegi-spring-security-and-rampart.html >> >> Thanks, >> >> >> On Sat, Dec 5, 2009 at 8:37 PM, Andreas Veithen >> <[email protected]> wrote: >> > As far as I know, there is no out-of-the-box integration between Axis2 >> > (and Rampart) and Acegi. >> > >> > Andreas >> > >> > On Fri, Dec 4, 2009 at 17:26, Philippe A. <[email protected]> wrote: >> >> Hello! >> >> >> >> I am currently reading on Acegi as we'd like to use it for our project. >> >> Does >> >> the axis2 standalone server have sufficient functionality to support >> >> Acegi? >> >> >> >> Thanks! >> >> >> > >> >> >> >> -- >> Sagara Gunathunga >> >> Blog - http://ssagara.blogspot.com >> Web - http://people.apache.org/~sagara/ > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
