Title: CAS redirection error
Last modified: November 11, 2020

---

# CAS redirection error

 *  Resolved [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * (@dgreene423)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/)
 * Last week I had to change my Apache root directory because I was running out 
   of space. CAS authentication worked before this. Regular WordPress logins work
   fine, but now CAS users are briefly seeing a too many redirects error page and
   then a UT CAS logout successful page or just stopping at a too many redirects
   page. Any ideas what may be happening here?
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcas-redirection-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Thread Starter [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * (@dgreene423)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-13659199)
 * From the Goggle dev tools it looks like the login is just bouncing back and forth
   from the wordpress login to [https://cas.tennessee.edu](https://cas.tennessee.edu)
   On other servers where I haven’t changed anything and use the same settings Authorizer
   and CAS log in continues to work fine.
 *  Plugin Author [Paul Ryan](https://wordpress.org/support/users/figureone/)
 * (@figureone)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-13660196)
 * Hm, it might be failing when the CAS client tries to find the ca-bundle.crt file(
   used to validate SSL certificates):
    [https://github.com/uhm-coe/authorizer/blob/master/src/authorizer/class-authentication.php#L753](https://github.com/uhm-coe/authorizer/blob/master/src/authorizer/class-authentication.php#L753)
 * Are you able to inspect whether the WordPress constants `ABSPATH` and `WPINC`
   are correctly pointing to the new location?
 * Also, a few lines down on the link above, you’ll see a commented out `setDebug()`
   call; you can try uncommenting that to output debug logs to `wp-content/debug.
   log` and see if there are helpful details in there. (You may want to change that
   path to something not publicly reachable if you’re doing it on a production server.)
   
   [https://github.com/uhm-coe/authorizer/blob/master/src/authorizer/class-authentication.php#L768](https://github.com/uhm-coe/authorizer/blob/master/src/authorizer/class-authentication.php#L768)
 * Finally, in your Apache config, do both `DocumentRoot` and the `<Directory /path/
   to/wordpress>` entry for WordPress point to the new location?
 *  Thread Starter [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * (@dgreene423)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-13660874)
 * All my paths look correct, the old path isn’t in the Apache conf files or the
   wp database and the ABSPATH and WPINC haven’t been modified from the defaults.
 * One login attempt (that of course fails) generates 523 lines in the debug log.
   I assume that’s not normal, but I don’t know enough about CAS to know what I’m
   looking at.
 * I doubt this has any bearing on the CAS problem but an older site on the same
   server that’s using Authorizer with LDAP works with no problem.
 *  Plugin Author [Paul Ryan](https://wordpress.org/support/users/figureone/)
 * (@figureone)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-13660887)
 * Yeah, the phpCAS logger is super chatty. Let us know when you get a chance to
   review it, it should at least contain the warnings or failure conditions.
 * You can also anonymize it and send it our way, but that may end up taking more
   effort since it tends to contain lots of user information from the CAS server.
 * It does seem like your issue is specific to CAS; will be interested to see how
   it might be related to the system path changes!
 *  Thread Starter [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * (@dgreene423)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-13695088)
 * I’ve put the log at [https://volweb.utk.edu/~dgreene/cas-log](https://volweb.utk.edu/~dgreene/cas-log)
   I can’t really follow the logic to tell what’s happening. If you spot anything,
   the help is appreciated.
 *  Plugin Author [Paul Ryan](https://wordpress.org/support/users/figureone/)
 * (@figureone)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-14005420)
 * In that log I see a system path for curl’s ca-bundle.crt lookup:
    `CURL: Set 
   CURLOPT_CAINFO /data/www/call.infosci/html/wp-includes/certificates/ca-bundle.
   crt [CurlRequest.php:129]`
 * Does that look like a valid (new) path to you? If not, that might be the issue!
 *  Thread Starter [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * (@dgreene423)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-14144019)
 * That’s the right path, I never have figured it out. I just moved the CAS authenticated
   sites off that server. The only sites left on that server are LDAP ones and they
   work fine.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘CAS redirection error’ is closed to new replies.

 * ![](https://ps.w.org/authorizer/assets/icon-256x256.jpg?rev=1967453)
 * [Authorizer](https://wordpress.org/plugins/authorizer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/authorizer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/authorizer/)
 * [Active Topics](https://wordpress.org/support/plugin/authorizer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/authorizer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/authorizer/reviews/)

 * 7 replies
 * 2 participants
 * Last reply from: [Dan Greene](https://wordpress.org/support/users/dgreene423/)
 * Last activity: [5 years, 2 months ago](https://wordpress.org/support/topic/cas-redirection-error/#post-14144019)
 * Status: resolved