Hi Scott

Yeah, the root cause is null unfortunately. I wonder if the exception is 
generic because my LDAP server (OID) doesn't throw back an error code that can 
be interpreted by CAS?

If, say, it did throw a meaningful exception, is there a nice way of 
redirecting the request, per exception? For example can I configure it to go to 
'changePassword.jsp' is a PasswordExpiredException is thrown?

Regards 

Richard 


Date: Wed, 30 Apr 2008 09:02:03 -0400
From: [EMAIL PROTECTED]
To: [email protected]
Subject: Re: Login Exception

Richard,

Have you checked what the route cause of the exception is (i.e. calling 
e.getCause())?  That may be the exception you want (though there may also not 
be a root cause).

-Scott


On Tue, Apr 29, 2008 at 10:32 AM, Richard Gundersen <[EMAIL PROTECTED]> wrote:






Hello

Has anyone had any success detecting an AccountLockedException or similar when 
authenticating against LDAP? 

I am playing around with the code, and modified the following method so that 
instead of swallowing the exception, it prints a stacktrace...


        BindLdapAuthenticationHandler.authenticateUsernamePasswordInternal

...the exception caught is:

       org.springframework.dao.DataAccessResourceFailureException: Unable to 
create DirContext


(when trying to login with a username whose account is disabled). 

I am using Oracle Internet Directory. Would Active Directory provide more 
details to CAS as to why the login failed?

Regards 

Richard 



Date: Mon, 28 Apr 2008 13:38:27 -0400
From: [EMAIL PROTECTED]
To: [email protected]

Subject: Re: [cas-dev] CAS3.0.7 + LDAP configuration -- urgent help request!!

Edward,

That's an extremely old version of CAS you're using. I would recommend 
upgrading to CAS 3.2.1, which would have those pom.xml files that you're asking 
about (they are a Maven2 thing).


-Scott


On Mon, Apr 28, 2008 at 11:59 AM, Edward Chen <[EMAIL PROTECTED]> wrote:

first, I have my CAS 3.0.7 up and running for mysql server.



I am using CAS 3.0.7. I plan to configure CAS 3.0.7 with LDAP. I have LDAP 
server.

Now when I refer to page http://www.ja-sig.org/wiki/display/CASUM/LDAP to help 
me configure and I find something missing in my CAS 3.0.7. I have few questions



1. Can CAS 3.0.7 configure LDAP or I have to upgrade to the most recent version?



2. If I want to configure CAS 3.0.7 to LDAP, I don't find porn.xml in webapps. 
How do I add porn.xml portion into it? Can I just copy porn.xml file into my 
CAS     3.0.7's webapps folder? if not, where do I add the following piece





<dependency>

    <groupId>${project.groupId}</groupId>

    <artifactId>cas-server-support-ldap</artifactId>

    <version>${project.version}</version>

</dependency>







3. where should I put the following code in deployerConfigCpntext.xml? I 
attached my deployerConfigCpntext.xml.for you to take a look if it's right I 
put that piece. Also, when I add the ldap part into deployerConfigCpntext.xml, 
do I need to comment out my  mysql connection bean?





4. I don't understand the following piece code from ldap



<property name="userName" value="{bind_username_goes_here}"/>

                   <property name="password" 
value="{bind_user_password_goes_here}"/>



Do I need to change anything above?





Edward


_______________________________________________

cas-dev mailing list

[EMAIL PROTECTED]

http://tp.its.yale.edu/mailman/listinfo/cas-dev




-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia

Get 5GB  of online storage for free! Get it Now! 

_______________________________________________

Yale CAS mailing list

[email protected]

http://tp.its.yale.edu/mailman/listinfo/cas




-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia

_________________________________________________________________
Search and win with BigSnapSearch.com 
http://www.bigsnapsearch.com
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to