Matthew:
You're having the "CAS-that-I-built-deployment-problem" :-) That's
why I still recommend you put the logging, the UI, the LDAP, etc.
aside. Use your newly installed Maven 2.0.9 and build the CAS
download overall. It automatically pulls the authenticator and builds
a CAS.war for you. When that deploys, add the logging. Do it again.
If you're successful, modify the UI for your CAS.war. Deploy. Test.
I'm purposely not trying to tell you what the error is. I want you to
understand how to find the reason why your Spring bean won't
instantiate. And, when your Spring bean doesn't instantiate, your
application that you built doesn't work. I'll look over these files
and reply if I see something obvious. I understand your pain there,
but if you start simple and add you'll be able to ask the list why
"this" configuration for this bean "classA" doesn't instantiate.
Simplify your CAS.war and deploy that successfully. You're building it.
Let me know that goes,
David
On 10/10/08, Matthew Jones <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> > Also, did you configure the Maven build of the CAS server to include
> > the LDAP authentication module?
> >
>
> I have modified the pom.xml file to include:
> <dependency>
> <groupId>org.jasig.cas</groupId>
>
> <artifactId>cas-server-support-ldap</artifactId>
>
> <version>${project.version}</version>
> </dependency>
> I am not aware of any additional build (as opposed to deployment)
> configuration that I need to do.
>
> > If you didn't, I still recommend that
> > you deploy CAS unaltered first and then customize.
> >
>
> I have deployed the war file that is shipped with the 3.3 download and then
> configured it to use LDAP and the Spring LDAP jars by manually copying them.
> The changes I have made are identical to that system I had running. The only
> difference now is that I am trying to build my own war file and deploy that.
> I could just run a vanilla build and deploy the resulting war file and see
> if that works but I had hoped that I was only taking a small step. Indeed, I
> have had to upgrade maven to 2.09 and then run the build. The log file was a
> change that I had forgotten about and easily fixed. The war file I deploy
> does have the LDAP jars as part of it which I was told would be added for me
> having changed to LDAP authentication. Maven is not a system I have any
> previous experience with but have assumed, form what I have been told,
> should just work once you have the right version of course. Obviously, I am
> experiencing some other basic error which I had hoped would be obvious from
> the log files.
>
> Do you recommend that I do indeed try and build a vanilla 3.3 war file?
> Obviously, that will need the change to the log file location to work but
> shouldn't need anything else right?
>
> >
> > > Hi. I've been implementing a CAS solution using 3.1.1 and LDAP to an
> > > Active Directory and unless you're a CAS expert I would recommend that
> > > you do things in steps.
> > >
> > > From your stacktrace, it's evident that you haven't configured
> > > something properly. If you have the time, you should back up on
> > > customizing anything until you've successfully deployed CAS with the
> > > InMemoryDaoImpl (without LDAP) and been able to navigate to /cas/login
> > > and get a successful banner.
> > >
> > > If you do not want to do things in steps, you need to start with the
> > > trace. Find the culprit Spring bean and start there. It's not
> > > obvious from the trace what you've done wrong. I'll say from
> > > experience that once you get CAS to work in it's default
> > > configuration, LDAP is next and it can be difficult. I think too that
> > > everyone's situation is always a little different than the how-to's
> > > that you find in the wiki. Or, you need to chose the right
> > > configuration for your house.
> > >
> > > Post your deployerConfigContext.xml and cas.properties here and I'll
> > > try to help.
> > >
> >
>
> Attached - deployerConfigContext.xml has obscured URL & OU (hence the XXX
> extension).
>
> In reality, I am trying to build a deployable .war file that has our
> configuration in having already gone through the "pain" of getting that
> configuration to work. That is, the LDAP authentication handler is working
> and with a changed image displayed on the login & logout pages. This is just
> the first step on the way to having to write a specific authentication
> handler to deal with certificate & username/password credentials and
> properly skinning CAS.
>
>
> Thanks
>
> --
> Matthew Jones
> Interactive Data Managed Solutions Ltd
> -----------------------------------------------------------------------
> Registered in England Company Number 3691868
> Registered Office: Fitzroy House, 13-17 Epworth Street, London, EC2A 4DL
> Tel: +44 (0)1242 694133 | Fax: +44 (0)1242 694109
> [EMAIL PROTECTED]
> http://www.interactivedata-ms.com/694133
>
> This message (including any files transmitted with it) may contain
> confidential and/or proprietary information, is the property of Interactive
> Data Corporation and/or its subsidiaries, and is directed only to the
> addressee(s). If you are not the designated recipient or have reason to
> believe you received this message in error, please delete this message from
> your system and notify the sender immediately. An unintended recipient's
> disclosure, copying, distribution, or use of this message or any attachments
> is prohibited and may be unlawful.
> Interactive Data (Europe) Ltd Registered No. 949387 England Registered
> Office: Fitzroy House 13-17 Epworth Street. London. EC2A 4DL
>
>
> cas.securityContext.serviceProperties.service=https://localhost:8443/cas/services/j_acegi_cas_security_check
> cas.securityContext.casProcessingFilterEntryPoint.loginUrl=https://localhost:8443/cas/login
> cas.securityContext.ticketValidator.casServerUrlPrefix=https://localhost:8443/cas
>
> cas.themeResolver.defaultThemeName=default
> cas.viewResolver.basename=default_views
>
> host.name=cas
>
> #database.hibernate.dialect=org.hibernate.dialect.OracleDialect
> #database.hibernate.dialect=org.hibernate.dialect.MySQLDialect
> database.hibernate.dialect=org.hibernate.dialect.HSQLDialect
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
