This shows my CNs and DCs when I run this in my command prompt.
C:\Users\username>dsquery user -name CAS*
"CN=CAStest,CN=Users,DC=test,DC=test2,DC=test3,DC=com"
Also, When i run ldap:\\ad1.test.test2.test3.com\ in my browser, it takes me to
an AD search box. So i'm assuming this is the correct ldap:\\ link.
I've attached my config file and also below is my cas.log when I attempt to
connect. Please let me know if anyone knows where my issue might be occuring?
The log file doesn't really give me any detail.
------------------------------------------------------
2011-03-22 13:03:20,049 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:03:20,049 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:05:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:05:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:07:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:07:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:09:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:09:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:11:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:11:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:13:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Reloading registered
services.
2011-03-22 13:13:20,033 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:13:32,049 INFO
[org.jasig.cas.util.AutowiringSchedulerFactoryBean] - Shutting down Quartz
Scheduler
2011-03-22 13:15:00,268 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] - Loaded 0 services.
2011-03-22 13:15:00,689 DEBUG
[org.jasig.cas.util.AutowiringSchedulerFactoryBean] - Autowired the following
triggers defined in application context:
[triggerJobDetailTicketRegistryCleaner, periodicServiceRegistryReloaderTrigger]
2011-03-22 13:15:02,346 INFO
[org.jasig.cas.util.AutowiringSchedulerFactoryBean] - Starting Quartz Scheduler
now
2011-03-22 13:15:02,643 DEBUG
[org.jasig.cas.services.web.ManageRegisteredServicesMultiActionController] -
Found action method [public org.springframework.web.servlet.ModelAndView
org.jasig.cas.services.web.ManageRegisteredServicesMultiActionController.deleteRegisteredService(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse)]
2011-03-22 13:15:02,643 DEBUG
[org.jasig.cas.services.web.ManageRegisteredServicesMultiActionController] -
Found action method [public org.springframework.web.servlet.ModelAndView
org.jasig.cas.services.web.ManageRegisteredServicesMultiActionController.manage(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse)]
2011-03-22 13:15:06,439 INFO [org.jasig.cas.web.flow.InitialFlowSetupAction] -
Setting path for cookies to: /cas
2011-03-22 13:15:06,439 INFO [org.jasig.cas.web.flow.InitialFlowSetupAction] -
Setting path for cookies to: /cas
2011-03-22 13:15:06,455 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:06,455 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:06,971 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:06,971 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:07,111 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:07,111 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:07,127 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:07,127 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,393 DEBUG
[org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler] - Performing
LDAP bind with credential:
uid=CAStest,cn=Users,dc=test1,dc=test2,dc=test3,dc=com
2011-03-22 13:15:16,549 INFO
[org.jasig.cas.authentication.AuthenticationManagerImpl] -
AuthenticationHandler:
org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler failed to
authenticate the user which provided the following credentials: [username:
CAStest]
2011-03-22 13:15:16,580 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,580 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,721 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,721 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,736 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:16,736 DEBUG [org.jasig.cas.web.support.SamlArgumentExtractor]
- Extractor did not generate service.
2011-03-22 13:15:20,627 INFO
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Beginning ticket cleanup.
2011-03-22 13:15:20,627 DEBUG
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Attempting to acquire ticket cleanup lock.
2011-03-22 13:15:20,627 DEBUG
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Acquired
lock. Proceeding with cleanup.
2011-03-22 13:15:20,627 INFO
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 0
tickets found to be removed.
2011-03-22 13:15:20,627 DEBUG
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Releasing ticket cleanup lock.
2011-03-22 13:15:20,627 INFO
[org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Finished
ticket cleanup.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
<?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";
xmlns:sec="http://www.springframework.org/schema/security";
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.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 declaration that every CAS deployer will need to change before deploying CAS
| into production. The default SimpleTestUsernamePasswordAuthenticationHandler authenticates UsernamePasswordCredentials
| where the username equals the password. You will need to replace this with an AuthenticationHandler that implements your
| local authentication strategy. You might accomplish this by coding a new such handler and declaring
| edu.someschool.its.cas.MySpecialHandler here, or you might use one of the handlers provided in the adaptors modules.
+-->
<!--
| This is the authentication handler declaration that every CAS deployer will need to change before deploying CAS
| into production.
| With this configuration you'll be using LDAP FastBind authentication.
+-->
<bean
class="org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler" >
<property name="filter" value="uid=%u,cn=Users,dc=test1,dc=test2,dc=test3,dc=com" />
<property name="contextSource" ref="contextSource" />
</bean>
<!--
<bean class="org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler">
<property name="users">
<map>
<entry>
<key>
<value>scott</value>
</key>
<value>secret</value>
</entry>
</map>
</property>
</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 Spring Security 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.
-->
<sec:user-service id="userDetailsService">
<sec:user name="@@THIS SHOULD BE REPLACED@@" password="notused" authorities="ROLE_ADMIN" />
</sec:user-service>
<!--
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" />
<bean id="contextSource" class="org.springframework.ldap.core.support.LdapContextSource">
<property name="urls">
<list>
<value>ldap:\\ad1.test.test2.test3.com\ </value>
</list>
</property>
<property name="userDn" value="cn=CAStest,cn=Users,dc=test1,dc=test2,dc=test3,dc=com"/>
<property name="password" value="c@sPassword"/>
<property name="baseEnvironmentProperties">
<map>
<entry>
<key>
<value>java.naming.security.authentication</value>
</key>
<value>simple</value>
</entry>
</map>
</property>
</bean>
</beans>
