We consider using CAS generated JWT instead of Service Ticket. We also face a proxy like use case described here <https://apereo.github.io/cas/5.3.x/installation/Configuring-Proxy-Authentication.html#use-case>. Why would we go into complexities of the CAS proxy call flow <https://apereo.github.io/cas/5.0.x/protocol/CAS-Protocol.html#web-flow-diagram> when user facing service may simply supply JWT to the secondary service instead of dealing with Proxy Ticket? Do we miss something here or indeed using JWT makes handling the proxy use case much simpler? Thank you for your opinion.
-- - 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/b28ed8a0-2270-4dba-b0d6-f26485a6b276%40apereo.org.
