CAS tickets length/format

[Marvin Addison]

On Thu, Apr 20, 2017 at 5:06 PM Mircea Baciu <mircea.baciu at simmons.edu>
wrote:

> Here's a ticket from IdP:
>
> ST-AAhzZWNyZXQyMLjnIZ_lGXRqhpMw2sKmON-CHB_KixeV_Mr35-aB46_zutFyEXiVESYYRgTX7JexOSd2MjxVFoe0fIwcTqf6bTQUjlHiJudA_GRbzXGtpXJzQEtJMtVVlKfPr7QSLP-ppxmE8RbMvB9SQuKmXb0bXinRTrpO4GM_jZkQBAOxARnHSEzN2ATd5qVgkfSHTGCTNs-fJJ-hzw1zJnURH8IDskoqN0xQkeOE--CDOPB5UpoMgeIIRKP9lZaJApg-mgANUzI4UnrFgpoUMpQRfpIHKt2wJX_dILBBtZqSs5VW7Hlw
>
> The CAS server ticket looks like this:
> ST-14868-0AvPvOss9kIUvFmCBhDi-login.simmons.edu
>
> My feeling is that the application's CAS client is not happy to see such a
> long ticket and that causes the error.
>

Sorry I missed this thread -- had my head down on other local projects. I
see you found the solution, but I wanted to add that during testing at my
institution I found much the same. Serializing the data into the ticket
string is a very beneficial feature if you can stand it, but there are many
clients that simply can't handle tickets outside the format used by the
Jasig CAS server. Ticket length and improper URL encoding were the most
common cases I found; seems you've found another with XML processing.

Best,
Marvin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170426/6069a7d4/attachment.html>