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/694133This 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
<?xml version="1.0" encoding="UTF-8"?> <!-- | deployerConfigContext.xml centralizes into one file some of the declarative configuration that | all CAS deployers will need to modify. | | This file declares some of the Spring-managed JavaBeans that make up a CAS deployment. | The beans declared in this file are instantiated at context initialization time by the Spring | ContextLoaderListener declared in web.xml. It finds this file because this | file is among those declared in the context parameter "contextConfigLocation". | | By far the most common change you will need to make in this file is to change the last bean | declaration to replace the default SimpleTestUsernamePasswordAuthenticationHandler with | one implementing your approach for authenticating usernames and passwords. +--> <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:p="http://www.springframework.org/schema/p"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> <!-- | This bean declares our AuthenticationManager. The CentralAuthenticationService service bean | declared in applicationContext.xml picks up this AuthenticationManager by reference to its id, | "authenticationManager". Most deployers will be able to use the default AuthenticationManager | implementation and so do not need to change the class of this bean. We include the whole | AuthenticationManager here in the userConfigContext.xml so that you can see the things you will | need to change in context. +--> <bean id="authenticationManager" class="org.jasig.cas.authentication.AuthenticationManagerImpl"> <!-- | This is the List of CredentialToPrincipalResolvers that identify what Principal is trying to authenticate. | The AuthenticationManagerImpl considers them in order, finding a CredentialToPrincipalResolver which | supports the presented credentials. | | AuthenticationManagerImpl uses these resolvers for two purposes. First, it uses them to identify the Principal | attempting to authenticate to CAS /login . In the default configuration, it is the DefaultCredentialsToPrincipalResolver | that fills this role. If you are using some other kind of credentials than UsernamePasswordCredentials, you will need to replace | DefaultCredentialsToPrincipalResolver with a CredentialsToPrincipalResolver that supports the credentials you are | using. | | Second, AuthenticationManagerImpl uses these resolvers to identify a service requesting a proxy granting ticket. | In the default configuration, it is the HttpBasedServiceCredentialsToPrincipalResolver that serves this purpose. | You will need to change this list if you are identifying services by something more or other than their callback URL. +--> <property name="credentialsToPrincipalResolvers"> <list> <!-- | UsernamePasswordCredentialsToPrincipalResolver supports the UsernamePasswordCredentials that we use for /login | by default and produces SimplePrincipal instances conveying the username from the credentials. | | If you've changed your LoginFormAction to use credentials other than UsernamePasswordCredentials then you will also | need to change this bean declaration (or add additional declarations) to declare a CredentialsToPrincipalResolver that supports the | Credentials you are using. +--> <bean class="org.jasig.cas.authentication.principal.UsernamePasswordCredentialsToPrincipalResolver" /> <!-- | HttpBasedServiceCredentialsToPrincipalResolver supports HttpBasedCredentials. It supports the CAS 2.0 approach of | authenticating services by SSL callback, extracting the callback URL from the Credentials and representing it as a | SimpleService identified by that callback URL. | | If you are representing services by something more or other than an HTTPS URL whereat they are able to | receive a proxy callback, you will need to change this bean declaration (or add additional declarations). +--> <bean class="org.jasig.cas.authentication.principal.HttpBasedServiceCredentialsToPrincipalResolver" /> </list> </property> <!-- | Whereas CredentialsToPrincipalResolvers identify who it is some Credentials might authenticate, | AuthenticationHandlers actually authenticate credentials. Here we declare the AuthenticationHandlers that | authenticate the Principals that the CredentialsToPrincipalResolvers identified. CAS will try these handlers in turn | until it finds one that both supports the Credentials presented and succeeds in authenticating. +--> <property name="authenticationHandlers"> <list> <!-- | This is the authentication handler that authenticates services by means of callback via SSL, thereby validating | a server side SSL certificate. +--> <bean class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler" p:httpClient-ref="httpClient" /> <!-- | This is the authentication handler specified in the CAS-LDAP documentaion +--> <bean class="org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler"> <property name="filter" value="uid=%u" /> <property name="searchBase" value="ou=OUR-OU,dc=interactivedata,dc=com" /> <property name="contextSource" ref="contextSource" /> </bean> </list> </property> </bean> <!-- | This bean defines the security roles for the Services Management application. Simple deployments can use the in-memory version. | More robust deployments will want to use another option, such as the Jdbc version. | The name of this should remain "userDetailsService" in order for Acegi to find it. | To use this, you should add an entry similar to the following between the two value tags: | battags=notused,ROLE_ADMIN | where battags is the username you want to grant access to. You can put one entry per line. +--> <bean id="userDetailsService" class="org.acegisecurity.userdetails.memory.InMemoryDaoImpl"> <property name="userMap"> <value> </value> </property> </bean> <!-- | Bean that defines the attributes that a service may return. This example uses the Stub/Mock version. A real implementation | may go against a database or LDAP server. The id should remain "attributeRepository" though. +--> <bean id="attributeRepository" class="org.jasig.services.persondir.support.StubPersonAttributeDao"> <property name="backingMap"> <map> <entry key="uid" value="uid" /> <entry key="eduPersonAffiliation" value="eduPersonAffiliation" /> <entry key="groupMembership" value="groupMembership" /> </map> </property> </bean> <!-- | Sample, in-memory data store for the ServiceRegistry. A real implementation | would probably want to replace this with the JPA-backed ServiceRegistry DAO | The name of this bean should remain "serviceRegistryDao". +--> <bean id="serviceRegistryDao" class="org.jasig.cas.services.InMemoryServiceRegistryDaoImpl" /> <!-- | This is the bean specified in the CAS-LDAP documentation +--> <bean id="contextSource" class="org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource"> <property name="pooled" value="true"/> <property name="urls"> <list> <value>ldaps://OUR-LDAP-SERVER-URL/</value> </list> </property> <property name="anonymousReadOnly" value="false"/> <property name="userName" value="uid=ldapbrowser,ou=idms,dc=interactivedata,dc=com"/> <property name="password" value="br0ws3r$"/> <!-- +--> <property name="baseEnvironmentProperties"> <map> <entry> <key> <value>java.naming.security.authentication</value> </key> <value>simple</value> </entry> </map> </property> </bean> </beans>
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
