Sorry I am not sure what to tell you. I assume your cas.properties file is located at /etc/cas/config/cas.properties. Also, you could try increasing the logging to see if anything interesting shows up in the logs. I don’t know how to list the currently registered services or even if it is possible.
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Pedro Rosas Sent: Saturday, September 22, 2018 10:17 PM To: CAS Community <cas-user@apereo.org> Subject: Re: [cas-user] Re: CAS5.1 ,Application Not Authorized to Use CAS , no service registry issue.??? Hi Doug, Thanks for your quick reply. I have tried your suggestion, but it also did not work. I can change the main css, using the overlay and creating the "/src/main/resources/static/css/cas.css". But I really wanted to have themes for each application. It seems to me that either the cas.properties or the myservice.json files are not being loaded. Do you know if there is any way I can "query" CAS to list the currently registered services? Best Regards, Pedro Rosas On Sunday, September 23, 2018 at 12:54:02 AM UTC+1, Doug C wrote: Pedro, I think you want to use cas.serviceRegistry.json.location=file:/etc/cas/services instead of cas.serviceRegistry.config.location: file:/etc/cas/services I am just looking at my configuration and that is what I have and I seem to remember this property name changing recently and this tripping me up. Give it a try. Doug From: cas-...@apereo.org <javascript:> [mailto:cas-...@apereo.org <javascript:> ] On Behalf Of Pedro Rosas Sent: Saturday, September 22, 2018 12:39 PM To: CAS Community <cas-...@apereo.org <javascript:> > Subject: Re: [cas-user] Re: CAS5.1 ,Application Not Authorized to Use CAS , no service registry issue.??? Hello, I'm using the latest version of CAS at the moment (5.3.3) and I want to customize the UI of the login screen. I followed the approach defined here https://apereo.github.io/2018/06/10/cas-userinterface-customizations on the "Themes" section. Summing up, these are the steps that I executed: 1. Git Clone of the CAS overlay template here https://github.com/apereo/cas-overlay-template 2. Switch to the 5.3 branch 3. Added the cas-server-support-json-service-registry dependency to the pom file on the "default" profile 4. Executed the mvnw clean package command 5. Added the "cas.serviceRegistry.config.location: file:/etc/cas/services" entry to the cas.properties file 6. Added the /etc/cas/services/myservice.json file with the "theme" property set to "mytheme" 7. Added the theme files to /src/main/resources/static/themes/mytheme: 1. /src/main/resources/static/themes/mytheme/css/cas.css 2. /src/main/resources/static/themes/mytheme/js/cas.js 8. Run the application on tomcat 9. Access to http://localhost:8080/cas-overlay/login?service=https://www.myservice.com as defined on step 6 Unfortunately, the only message I receive is "Application Not Authorized to Use CAS". Do you guys have any idea what I could be missing? I have deeply searched this issue and applied many suggestions but nothing seems to help.. I have tried CAS 5.3.2 but no success too. Thanks. Best Regards, Pedro Rosas On Tuesday, September 5, 2017 at 4:27:37 PM UTC+1, Doug C wrote: Thanks! That is really odd. I tried that earlier but couldn't get it to work so I just reverted to storing it in the classpath. Maybe I just messed something up though when I was testing as I am testing a lot of things that are new to me as I try to update my very old CAS 3.x to 5.1.3. More odd is that I don't have the dependency added in my pom.xml file, I only set cas.serviceRegistry.initFromJson=true and that was enough to have my service definition read from the classpath;/services directory. On Tuesday, September 5, 2017 at 11:19:32 PM UTC+8, David Curry wrote: You're mixing two different things. The bug fix (more of a feature enhancement) you describe was to the automatic service registry initialization feature described here: https://apereo.github.io/cas/development/installation/InMemory-Service-Management.html#auto-initialization <https://www.google.com/url?q=https%3A%2F%2Fapereo.github.io%2Fcas%2Fdevelopment%2Finstallation%2FInMemory-Service-Management.html%23auto-initialization&sa=D&sntz=1&usg=AFQjCNEzU12Ry5xghNB4LpmwDRjQ2frs2A> That's not (at least as I understand it) the same thing as the JSON service registry itself, which is added with a separate dependency as I described (although it probably gives you the same result). Adding the dependency to pom.xml: <dependency> <groupId>org.apereo.cas</groupId> <artifactId>cas-server-support-json-service-registry</artifactId> <version>${cas.version}</version> </dependency> and re-running mvnw clean package, and then adding cas.serviceRegistry.config.location: file:/etc/cas/services to cas.properties and then making a service description like this in /etc/cas/services/wildcard.json (or whatever): { /* * Wildcard service definition that applies to any https or imaps url. * Do not use this definition in a production environment. */ "@class" : "org.apereo.cas.services.RegexRegisteredService", "serviceId" : "^(https|imaps)://.*", "name" : "HTTPS/IMAPS wildcard", "id" : 20170905111650, "evaluationOrder" : 99999 } should work. Don't forget to restart the server. :-) At least, it works just fine for me on CAS 5.1.3. When the CAS login page is displayed, you should see whatever string is in the name field of the JSON displayed at the top right of the page in a light blue box. That's how you know which registry entry matched. --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...@newschool.edu <javascript:> <https://lh4.googleusercontent.com/proxy/kBxyNqPE_dwGnQ5_31vxODZ361V2PjQdxLgStd_Hjq6qhsUZ5Ls9wt8E7q_K2I1IH9Gl9beQOC7lRFhDZ6YS4RBwSzHk1J04dgKAuT9_k0gSpkU-gvRxyA=w5000-h5000> On Tue, Sep 5, 2017 at 10:55 AM, Doug C <wdouglas...@gmail.com <mailto:wdouglas...@gmail.com> > wrote: 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...@newschool.edu <javascript:> <https://lh4.googleusercontent.com/proxy/kBxyNqPE_dwGnQ5_31vxODZ361V2PjQdxLgStd_Hjq6qhsUZ5Ls9wt8E7q_K2I1IH9Gl9beQOC7lRFhDZ6YS4RBwSzHk1J04dgKAuT9_k0gSpkU-gvRxyA=w5000-h5000> On Tue, Sep 5, 2017 at 7:47 AM, Doug C <wdouglas...@gmail.com <mailto:wdouglas...@gmail.com> > 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 <mailto:cas-user+u...@apereo.org> . 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+u...@apereo.org <mailto:cas-user+u...@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 <https://groups.google.com/a/apereo.org/d/msgid/cas-user/d550fcb5-efa4-4720-99bf-5a0e88184da5%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+u...@apereo.org <javascript:> . To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6e9f1089-c3ac-4446-bddf-09697f4ba97f%40apereo.org <https://groups.google.com/a/apereo.org/d/msgid/cas-user/6e9f1089-c3ac-4446-bddf-09697f4ba97f%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 <mailto:cas-user+unsubscr...@apereo.org> . To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/c75906c4-a881-4382-a6ce-8c23db6fb08e%40apereo.org <https://groups.google.com/a/apereo.org/d/msgid/cas-user/c75906c4-a881-4382-a6ce-8c23db6fb08e%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/003b01d452f4%24be5c39c0%243b14ad40%24%40gmail.com.
