Hi Konstantin,
If you have complete control over the client, then the JWT route may indeed be 'easier'. Until v5.3.7, one limiting factor was that all JWTs were created using a single set of signing & encryption keys. That implementation doesn't allow for JWTs to be distributed to many different 3rd parties, over which we have little control. Fortunately, v5.3.7 was re-architected to allow for per-service JWT keys, and this shouldn't be an issue any more.
Thinking about it for a moment:
* Using a JWT 'freezes' into the two keys the method of establishing trust between parties. By that, I mean that you would have to re-configure CAS to use new keys AND then re-configure the client.
* Using the CAS ServiceTicket method of establishing trust is more 'dynamic' as it requires the client to validate the ServiceTicket in each authentication session, but no re-configuration would be necessary if the keys were compromised.
Kind regards,
Drew