Announcement Announcement Module
No announcement yet.
Migrating to Spring Security from Acegi Page Title Module
Move Remove Collapse
This topic is closed
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Migrating to Spring Security from Acegi

    I am migrating from acegi to Spring Security and using Spring Security 2.0.3
    with CAS server 3.2.1 and cas-client-core-3.1.3 .
    Earlier when I was using Acegi , I was using CasAuthenticationHandler as my
    authentication handler in deployConfigContext.xml. But it is not part of
    Spring Security now.Is there any equivalent handler in CAS ?
    Earlier I had to provide trustStore path to CasProxyTicketValidator , is
    this not required now any more ? Now I am using Cas20ServiceTicketValidator.
    If I dont provide trustStore , I am getting the following error :

    Cas20ServiceTicketValidator,http-8443-Processor24:49 - java.lang.RuntimeException: Unexpected error: the trustAnchors parameter
    must be non-empty .

    Can I find somewhere any working sample config files where JA SIG client for
    Java is implemented along with Spring Security ?


  • #2
    Same question

    I have also recently migrated from Acegi to Spring Security with CAS. I have it all running fine using the cacerts in my JVM. But I would like to be able to point my client to a alternate keystore. This was possible before using the trustStore on the CasProxyTicketValidator, but I have yet to find anyway to do it with the new Spring Security release and Cas_client_3.1. Anyone have any ideas?


    • #3
      Which server you are using ? In my case I was using Tomcat . So adding these to Apache Tomcat propertiesí java option solved my purpose :\java\jdk1.5.0_09\jre\ lib\security\cacerts (your path) path

      Cheers !!