I changed my CAS server to point at an Active Directory server (which I really 
don't much about) and now I can't authenticate.  I know that my LDAP server and 
the AD server are kept in sync.

I am not sure where the problem is.

My first thought is that I don't have the proper DN / password for the active 
directory.  I tried to prove the point by purposely configuring  a bogus 
password in the deployer config xml file.  I thought I might then get some 
error message telling me my credentials for AD were bad.  But this doesn't 
happen.

My second thought is that there is some certificate weirdness between my CAS 
server and AD.  But I am not getting any kind of errors in the CAS server log 
file.

I am a bit confused how to config log4j to up the number of messages because of 
these seemingly contradictory comments:

>From web.xml:

<!-- Leave the listener commented-out if using JBoss -->
                <listener>
                                <listener-class>
                                                
org.springframework.web.util.Log4jConfigListener
                                </listener-class>
                </listener>

And  log4j.properties:


# For JBoss: Avoid to setup Log4J outside 
$JBOSS_HOME/server/default/deploy/log4j.xml!
# For all other servers: Comment out the Log4J listener in web.xml to activate 
Log4J.

I am NOT using JBOSS.


-- 
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

Reply via email to