The wpCAS plugin appears to be working: I have a subdomain on a website which contains the WordPress installation (i.e.
test.mywebsite.com), and I'm running through a WordPress GitHub Repo along with Capistrano for actual deployment. This is important because, due to this setup, the content is within a subdirectory, i.e.
test.mywebsite.com/wp. The result is that, in order to access the site's admin section, I have to input
test.mywebsite.com/wp/wp-admin in my browser. Accessing the frontend website, however, only requires that I input
test.website.com. Confusing enough?
I'm testing all of this with a localhost MAMP server. It should also be worth nothing that I have also redirected the IP of
test.mywebsite.com to my local box via my Mac's
hosts file, so everything is correctly taking place on the local box.
Now, here's the catch: I'm using the wpCAS plugin with a RubyCAS server. Everything works up until the actual login process.
wpCAS is designed to simply re-direct the login page to my CAS login, and then match the credentials typed into the CAS interface with those in WordPress's database. If there's a match, it (theoretically) would bring me to the admin page with my credentials logged in and working correctly.
As a result of this setup, my typing in
localhost/wp/wp-admin takes me to
auth.mywebsite.com, the CAS interface where I can input my credentials.
However, once I put my credentials into the CAS interface I'm instead hit with a redirect loop that looks like:
so around and around we go!
Any idea why this would happen and how to solve the problem?