Actually, when I did that, it did not work. This appears to be a bug that has been fixed in CAS 5.2.0 RC2 as mentioned at https://apereo.github.io/2017/08/04/520rc2-release/#minors.
"Service registry initialization from JSON is now able to honor service definitions found at the path specified via settings, rather than only loading those found on the classpath’s services directory." On Tuesday, September 5, 2017 at 8:11:59 PM UTC+8, David Curry wrote: > To use a separate JSON registry (e.g., /etc/cas/services/), you have to > add the > > cas-server-support-json-service-registry > > > dependency to pom.xml and rebuild the server. Then you can set > > cas.serviceRegistry.config.location: file:/etc/cas/services > > > and put your service declarations in there. > > See > https://apereo.github.io/cas/5.1.x/installation/JSON-Service-Management.html > for the full documentation. > > --Dave > > > -- > > DAVID A. CURRY, CISSP > *DIRECTOR OF INFORMATION SECURITY* > INFORMATION TECHNOLOGY > > 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003 > +1 212 229-5300 x4728 • david.cu...@newschool.edu <javascript:> > > [image: The New School] > > On Tue, Sep 5, 2017 at 7:47 AM, Doug C <wdouglas...@gmail.com > <javascript:>> wrote: > >> I had this happen as well. I fixed it by adding the following line to >> the overlay etc/cas/config/cas.properties file: >> >> cas.serviceRegistry.initFromJson=true >> >> This seemed to cause the default service registry description files to be >> read in but they only allow HTTPS and IMAPS services. So in addition I >> also created the following directory structure in the overlay: >> src/main/webapp/WEB-INF/classes/services/ and then added a file named >> HTTP-10000003.json with the following content: >> >> { >> /* >> Generic service definition that applies to http urls >> that wish to register with CAS for authentication. >> */ >> "@class" : "org.apereo.cas.services.RegexRegisteredService", >> "serviceId" : "^http://.*";, >> "name" : "HTTP", >> "id" : 10000003, >> } >> >> By adding this extra service definition I was also able to use CAS with >> my HTTP urls as well. >> >> Note: I also tried to set >> cas.serviceRegistry.config.location=file:/etc/cas/services in the >> cas.properties file and then place the new service definition file there >> but it never seemed to want to read it. I think I did stumble across one >> bug report that indicated that setting it to anything besides >> classpath:/services wasn't working but that it was fixed in the v5.2.0. >> >> -- >> - 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 cas-user+u...@apereo.org <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/a/apereo.org/d/msgid/cas-user/1e82ca7c-aecf-4940-8f33-072857afed7a%40apereo.org >> >> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/1e82ca7c-aecf-4940-8f33-072857afed7a%40apereo.org?utm_medium=email&utm_source=footer> >> . >> > > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/d550fcb5-efa4-4720-99bf-5a0e88184da5%40apereo.org.
