Building CAS

[Matthew Jones]

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
matthew.jones at interactivedata.com
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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cas.properties
Url: http://tp.its.yale.edu/pipermail/cas/attachments/20081010/849ee741/attachment.pl 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: deployerConfigContext.xml.XXX
Type: text/xml
Size: 7966 bytes
Desc: not available
Url : http://tp.its.yale.edu/pipermail/cas/attachments/20081010/849ee741/attachment.xml 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2690 bytes
Desc: S/MIME Cryptographic Signature
Url : http://tp.its.yale.edu/pipermail/cas/attachments/20081010/849ee741/attachment.bin