CAS Login Redirect Issue upon Deployment

[caseywatts]

Every time we deploy a new instance of reservations we get caught in a redirect loop with the CAS login server. It seems that once we've successfully been to the CAS server once it will work. In the Chrome inspector's Network tab it shows the redirect to the CAS server and the redirect back. I just click on the link to the CAS server and that fixes it at least on my computer. I suspect it works on other computers too since Michael Dunlap didn't mention otherwise, but I didn't confirm.

I suspect URI encoding, and I noticed this relevant line in the rubycas-client documentation

...Note that you should always URI-encode your service parameter inside URIs!

maybe that's relevant?

I think I can reproduce this reliably by re-deploying to the development server, so I'll work on this issue.

[caseywatts]

rubycas-client-rails is a little old and not updated recently, so I'm a little skeptical.

I just tried the more maintained rubycas-client instead of rubycas-client-rails but it was a little harder to setup and not quite worth it. I think we can pass the extra parameters to rubycas-client-rails if we'd like though!

[caseywatts]

I'm out of URLs to try, they all work again :/

It seems like after we're able get to the CAS server successfully even once the issue is solved forever. Maybe the CAS server 'remembers' the url and can parse it all of a sudden?

As far as I can tell we're URI encoding it successfully, here's an example:
https://secure.its.yale.edu/cas/login?service=http%3A%2F%2Fdevelopment.reservations.yale.edu%2Fstc%2F

[caseywatts]

Could this be relevant?
rubycas/rubycas-client-rails#17

[caseywatts]

Only sorta relevant, but we don't have this documented anywhere else.

We're currently set to gem 'rubycas-client', '2.2.1', and this explains why we haven't upgraded that:
rubycas/rubycas-client-rails#6

[caseywatts]

Called Howard Gilbert who knows a lot about the CAS server at Yale, and he explained to me how CAS works a little more so I have a better idea of what to look for. On the next deployment we do I'll try to take more thorough notes.

[mnquintana]

Should we be upgrading our rubycas-client?

[caseywatts]

We could try the edge version from github?

[orenyk]

I believe we figured out that this had to do with the AppConfig checks for new instances (see #684) - closing!