Core dev Misagh Moayyed mentioned that this is a bug: 
https://stackoverflow.com/questions/59368162/cas-rest-protocol-does-not-work-without-generic-service-definition/

So a solution is to register your CAS instance(s) as a service until the 
bug is resolved. (In case you don't use generic service regex which was in 
my case, so CAS instance was not matching as registered service, which was 
throwing exception)

-- 
- 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/368495d1-bc93-4283-a3f1-75f9013e6837%40apereo.org.

Reply via email to