We're on 5.3.11. Struggled with this as well, could never find a third
party tool or library that could validate the jwt generated by cas. I even
contact the maintainer of one of the python libs and he claims the cas
generated JWT was invalid. I was able to write my own java to validate
base
Also, this was working in 5.1.3, but, of course, with the 'old style'
properties, before the New Order with *.crypto.* was implemented.
Drew
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https
@Cyrus , FWIW, we have the same issue, but with 5.3.x. The docs are
confusing. In our case, we have both:
cas.authn.token.crypto.encryptionEnabled=true
cas.authn.token.crypto.signingEnabled=true
but not
cas.authn.token.crypto.enabled=true
and that doesn't work either.
Drew
--
- Website: http
