Fabian,

I suggest you turn up logging to at least debug until you are ready to move to 
production. If I remember correctly, the service location is logged on start up.

Previous advice still stands but add this:

        <!-- INFO Loaded [#] service(s) from [???ServiceRegistryDAO]
             DEBUG Adding registered service [service URL] -->
        <AsyncLogger name="org.apereo.cas.services.AbstractServicesManager" 
level="debug" />

Ray

On Fri, 2019-06-07 at 02:10 -0700, Fabian Schipp wrote:
I tried both now, but there seems to be no difference.
I have noticed however that whatever I put into the 
<cas-war-repo>/etc/cas/services or /etc/cas/services the output always states 2 
services being loaded from the JSON Registry. Even if I delete all services 
from those folders, clean build and run.
2019-06-07 11:01:43,051 INFO [org.apereo.cas.services.AbstractServicesManager] 
- <Loaded [2] service(s) from [JsonServiceRegistry].>

I would like to see what services these are and tried to enable the actuator 
registeredServices using these properties 
(https://apereo.github.io/cas/6.0.x/configuration/Configuration-Properties.html#actuator-management-endpoints):
management.endpoints.enabled-by-default: true
management.endpoints.web.base-path:     /actuator
management.endpoints.web.exposure.include:      
info,health,status,configurationMetadata,registeredServices

But the actuator is not available after booting on 
<cas-url>/cas/actuator/registeredServices

Am Freitag, 7. Juni 2019 09:39:19 UTC+2 schrieb Matthew Uribe:
In my experience that is not the same as /etc/cas/services. I would recommend 
you change that to /etc/cas/services explicitly and restart.

On Friday, June 7, 2019 at 1:29:30 AM UTC-6, Fabian Schipp wrote:
The cas.properties contains this line:
cas.serviceRegistry.json.location:      classpath:/services

This should refer to /etc/cas/services. Wich is the location my services are 
stored.
Also the build.gradle file contains the corresponding dependency
compile 
"org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"



Am Donnerstag, 6. Juni 2019 20:14:39 UTC+2 schrieb Matthew Uribe:
Is there any other simplistic service I could try to see if CAS loads anything 
correct?

That same tutorial you mentioned contains steps for setting up a basic CAS or 
SAML client in order to test your CAS server.

Since you don't have any other services currently working with this CAS server, 
I would just ask you to confirm that your json files are in the location 
specified in your cas.properties cas.serviceRegistry.json.location line.

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | [email protected]<mailto:[email protected]>

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- 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/7107c94ba4bc7d8dc3b75267ebaaa28d017a3ba4.camel%40uvic.ca.

Reply via email to