READ this BEFORE you start working on ACEGI

May 2007 Blogged by Allan Tan

I’ve seen several implementations of ACEGI on enterprise applications. However, I’ve never setup one myself until earlier today… At first, I was quite frustrated with the spring configuration as none seems to work. After looking at several articles online, I get more frustrated as everyone talks about different syntax.

So, I’ve thought of writing down some documentation on how to make ACEGI work seamless with Spring and Hibernate but then I’ll just be adding more confusion to all available articles on the net. So instead of writing step-by-step instructions, I’ll just give out pointers on how to make your learning experience easier.

Rule #1: Follow the Petclinic examples provided from the build – with the exact build number! It seems that there are name changes in ACEGI on different releases. This means that you could be reading an article about ver. 0.8 which is not applicable on ver.1.0, etc. There are differences even on minor releases (1.0.2 to 1.0.4). So stick with the tutorial that comes with build and copy the spring-config from the tutorial as is.

Rule #2: Understand the security framework. Spend a few hours studying the ACEGI configuration. This will save you time later. I tried implementing ACEGI right away and whenever I get lost, I have to dig around and learn the concepts. I believe that its much easier to read and understand first before beating yourself out… I find this article very helpful: http://www.tfo-eservices.eu/wb_tutorials/pages/spring-acegi-tutorial.php But don’t take the configurations from this tutorial as some have changed since 1.0.2 to 1.0.4. Just learn the concepts and again – USE THE PETCLININC EXAMPLE FROM THE BUILD.

Rule #3: Get ACEGI working using InMemoryDaoImpl. Divide your work by focusing on getting the security features working before integrating this with your user DB or AuthenticationService. This way you can isolate your issue to ACEGI settings only. Note: The PETCLINIC example uses MD5PasswordEncoder for password, you need to disable this by removing PasswordEncoder property in your DaoAuthenticationProvider.

Rule #4: Do not wrap settings on ACEGI properties. ACEGI settings are sensitive on newlines, it will not recognize the text if configurations are wrapped. You cannot remove append the lines nor create newlines… if configuration text is long, leave it as is otherwise, ACEGI will not recognize it. While this may seem obvious, I got caught with this problem when I used auto-format in Eclipse.

Well… This is all I have for now…. good luck learning ACEGI!



Related Posts with Thumbnails

Thanks for rating this! Now tell the world how you feel - .
How does this post make you feel?
  • Excited
  • Fascinated
  • Amused
  • Bored
  • Sad
  • Angry

8 Responses to “READ this BEFORE you start working on ACEGI”

  1. July 24, 2007  -  10:46 am
    Karl Moore

    I would also add, have a look at the acegi-security-sample-tutorial example. Lots of people I’ve introduced to Acegi can pretty much plug this straight into their application. The typical changes required are protecting the right pages and swaping out the InMemoryDaoImpl for the JdbcDaoImpl. For lots of people it is that simple!

  2. July 24, 2007  -  6:16 pm
    allanctan

    Yeah, just make sure to use the same versions (examples, libs, docs) because there are configuration changes even on minor versions.

  3. August 23, 2007  -  4:59 am
    sheeba

    How to implement JDBCDaoImpl.Can any one give me some samples?

  4. August 23, 2007  -  7:10 am
    allanctan

    I have to reiterate, your best resource is the sample implementation included in your ACEGI version.

    Once you get InMemoryDAOImpl working, you can add DAO implemention like the one I use:

     


     

    In the example above , I’ve overridden the default SQL statements of ACEGI. But you can use the default queries included in the sample.

  5. September 30, 2007  -  7:55 pm

    Hi I’m new on acegi,
    and I wanna use JDBCDaoImpl,

    is my dispatcher config is right ??, coz it appears error when I reload the sample using
    this config.

    here is :

    Welcome to the Demo App!!

    false

    simplePersonForm

    springweb.form.SimplePersonForm

    initparamsubmit

    /secure/app/paramsubmit.htm

    indexController
    logoutController

    initParamSubmitController

    paramSubmitController

    initAdminController

    /WEB-INF/springweb-views.xml


    CONVERT_URL_TO_LOWERCASE_BEFORE_COMPARISON
    PATTERN_TYPE_APACHE_ANT
    /**=httpSessionContextIntegrationFilter,formAuthenticationProcessingFilter,exceptionTranslationFilter,filterSecurityInterceptor

    Spring Web Realm

    /j_acegi_security_check

    /loginFailed.html

    /

    /login.jsp

    false


    CONVERT_URL_TO_LOWERCASE_BEFORE_COMPARISON
    PATTERN_TYPE_APACHE_ANT
    /secure/admin/*=ROLE_ADMIN
    /secure/app/*=ROLE_USER

    Select username,password,enabled FROM USERS WHERE username=?

    Select username,authority from AUTHORITIES where username=?

    jklaassen=4moreyears,ROLE_ADMIN
    bouerj=ineedsleep,ROLE_USER

    –>

    ROLE_

    com.mysql.jdbc.Driver

    jdbc:mysql://localhost:3306/acegi

    root

    praweda

  6. September 30, 2007  -  8:04 pm

    sorry the config couldn’t display well,

    here is my config :

    http://kahlilstt.blogsome.com/2007/10/01/my-dispatcher/

    please help me!

  7. November 7, 2007  -  12:05 am

    xrumer is the best program for advertisement!
    It’s have CAPTCHA recognizer, email verificator, and a lot of other functions…

    But. I forgot link to it 🙁

    Can you give me link to the XRumer description? screenshots, etc.

    Thank you

  8. December 20, 2007  -  3:57 am

    I would like to see a continuation of the topic

Leave a Reply


!-- GOOGLE ANALYTICS -->