It might be that the default on the validation filter is to redirect after validation success.
Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Willem Toorop <[email protected]> Date: Wed, 20 Jan 2010 20:32:59 To: <[email protected]> Subject: Re: [cas-user] Trying to get clearPass to work Hi Scott, Those are the instructions I followed. I did it with cas-server-3.3.5-release. Then I encountered this bug: http://www.ja-sig.org/issues/browse/CASC-88 I fixed it by manually removing cas-client-core-3.1.3.jar from the webapps WEB-INF/lib directory, because cas-client-core-3.1.9.jar was also there. Is that the extra jars problem you're referring to? It just seems strange to me that everything seems to go well, but that the /clearPass?ticket=ST-blabla request redirects to /clearPass in stead of returning a response. No error messages are logged. Here are the entries in cas.log: 2010-01-20 20:29:10,735 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - AuthenticationHandler: org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler successfully authenticated the user which provided the following credentials: [username: w.toorop] 2010-01-20 20:29:10,807 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - Granted service ticket [ST-77-G3ibGeUeEeKX7AeiY4Kd-cas] for service [ http://uportal3.ahk.nl/php/casproxy.php] for user [w.toorop] 2010-01-20 20:29:15,459 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - AuthenticationHandler: org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler successfully authenticated the user which provided the following credentials: [callbackUrl: https://uportal3.ahk.nl/php/casproxy.php] 2010-01-20 20:29:17,212 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - Granted service ticket [ST-78-rPQPlhtZNS54f9t9Tff9-cas] for service [https://login.ahk.nl/clearPass] for user [https://uportal3.ahk.nl/php/casproxy.php] 2010-01-20 20:29:18,217 INFO [org.jasig.cas.client.proxy.ProxyGrantingTicketStorageImpl] - No Proxy Ticket found for 2010-01-20 20:29:19,664 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - Granted service ticket [ST-79-apHcYFHC0SZ1KBqWkXw7-cas] for service [https://login.ahk.nl/clearPass] for user [https://uportal3.ahk.nl/php/casproxy.php] 2010-01-20 20:29:20,462 INFO [org.jasig.cas.client.proxy.ProxyGrantingTicketStorageImpl] - No Proxy Ticket found for The last line I understand, because that is the response the the /clearPass request without a tickit, but the lines before that don't seem to mention the service where the proxy ticket should be generated for. Is that bad? Thanks so far & Cheers, Willem 2010/1/20 Scott Battaglia <[email protected]> > Did you try these instructions: > http://www.ja-sig.org/wiki/display/CASUM/ClearPass > > There is one issue with the latest 3.3.5 release in combination with > ClearPass (with regards to extra jars appearing in the web app). The issue > should be fixed in 3.4. > > Cheers, > Scott > > > On Wed, Jan 20, 2010 at 10:54 AM, Willem Toorop <[email protected]> wrote: > >> Hi, >> >> I'm trying to get clearPass to work. I think I followed all the >> steps correctly, but now it is not really clear to me how to use it. >> >> From the documentation on >> http://www.ja-sig.org/wiki/display/CAS/Proxying+clear-text+credentialsI >> suspected that to acquire a password, one should simply call the >> /clearPass url giving it the Proxy Ticket with a ticket= parameter, but when >> I do this, clearPass will eventually redirect to the /clearPass url without >> parameters, which returns "No authentication information provided." >> >> Should the /clearPass be called with additional parameters? What are they? >> I couldn't find the documentation for this. >> >> All other CAS functionalities seem to work fine. >> >> Attached you'll find my CAS configuration and clearPass test >> php application. >> Also an capture of the network flow to the CAS server is attached in >> file tcpflow.log.txt. >> >> Am I doing something wrong? >> Thanks! >> >> Willem >> >> -- >> 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 >> >> > -- > 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 > > -- 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 -- 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
