We have another strange issue with our CAS 5.0 to 6.3 upgrade. We have a
homebrew regression test for 5.0 that parsed the HTML for the service
ticket from the Location header in a 302 redirect response after
authentication. E.g.:

Location:
https://casdemo.example.edu/casdemo/login/cas?ticket=ST-2-ujMo86d2pYcEebVDEFzWvAKghxE-cas

But with our 6.3 instance, we don't seem to see this 302 and Location
header after authentication from our homebrew test. Nor do the logs show an
ST being issued after an apparently successful authentication from the
test. Browser developer tools seem to show a number of scripts being
executed after authentication via "normal" sample client. Is the missing ST
perhaps because we don't execute these scripts in our regression test? If
so, can anyone tell us which script is responsible, or a possible
workaround?
-- 
Baron Fujimoto <[email protected]> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAAjLUL2-xuxeZ%3Dhyb1nvgGYKRF9poiX%3DamVPgXHGC4vW8nJfeQ%40mail.gmail.com.

Reply via email to