University Of Kansas
Hi Sourabh,
Guess 1:
1. CAS is generating the Service Ticket before displaying the password expiry interstitial.
2. Working through the password expiry interstitial requires nonzero time.
3. At the end of that interstitial, the service ticket the user presents to uPortal has expired, such that
4. uPortal falls back on the not-logged-in experience.
Guess 2:
Goofy CAS password expiry experience configuration such that it forgets or mangles the service URL somewhere in the flow. CAS server's understanding of the service parameter associated with a service ticket must match the CAS client's understanding of this, or ticket validation will fail.
Suggestion:
The Java CAS client and uPortal CAS support has some logging in it, as does CAS server. Crank up the logging configuration, observe success and failure, and compare logs.
Kind regards,
Andrew