I found !

in cas.properties 
cas.*service-registry*.json.location=file:/etc/cas/services

is not good for cas 6.1 but doesn't produce an error ....

the good way :
cas.serviceRegistry.initFromJson=true
cas.serviceRegistry.json.location=file:/etc/cas/services


Le jeudi 7 novembre 2019 11:18:43 UTC+1, ratm a écrit :
>
> Hello,
>
> On your cas 5.3 example json file are under 
> cas-overlay-docker/etc/cas/config/services/Everything-1.json 
>
> But with cas-overlay-template-6.1 the structure is :
> cas-overlay-template-6.1/etc/cas/services
>
> with cas-overlay-template-6.1 where should we put the json files ? ......
>
>
> Le jeudi 7 novembre 2019 10:40:10 UTC+1, ratm a écrit :
>>
>> Hello,
>>
>> The only log i have concerning services :
>>
>> 2019-11-07 10:25:29,447 INFO 
>> [org.springframework.boot.autoconfigure.security.servlet.UserDetailsServiceAutoConfiguration]
>>  
>> - <
>>
>>
>> 2019-11-07 10:25:30,792 WARN 
>> [org.apereo.cas.config.CasCoreServicesConfiguration] - <Runtime memory is 
>> used as the persistence storage for retrieving and persisting service 
>> definitions. Changes that are made to service definitions during runtime 
>> WILL be LOST when the CAS server is restarted. Ideally for production, you 
>> should choose a storage option (JSON, JDBC, MongoDb, etc) to track service 
>> definitions.>
>>
>>
>> 2019-11-07 10:25:31,958 INFO 
>> [org.apereo.cas.services.AbstractServicesManager] - <Loaded [0] service(s) 
>> from [InMemoryServiceRegistry].>
>>
>>
>> Cheers,
>>  Anthony
>>
>> Le mardi 5 novembre 2019 19:18:21 UTC+1, rbon a écrit :
>>>
>>> Anthony,
>>>
>>> Good. Properties are being read from where you expect them.
>>> With the correct set of properties, is there anything in the logs that 
>>> indicates where services are being read?
>>>
>>> Ray
>>>
>>> On Tue, 2019-11-05 at 09:06 -0800, ratm wrote:
>>>
>>> Thanks for help !
>>>
>>> When i introduce an error on registry property application doesn't start 
>>> !
>>>
>>>
>>> Le mardi 5 novembre 2019 17:50:21 UTC+1, rbon a écrit : 
>>>
>>> Anthony,
>>>
>>> Verify that your properties are being read (simple approach is introduce 
>>> a spelling mistake). Turn up logging to debug at least. Also check the 
>>> tomcat settings logs. All available in catalina.out by default.
>>>
>>>         <AsyncLogger name="org.apereo" level="${sys:cas.log.level}" 
>>> includeLocation="true"/>
>>>
>>> Ray
>>>
>>> On Tue, 2019-11-05 at 07:47 -0800, ratm wrote:
>>>
>>> I have added 
>>>
>>> cas.service-registry.json.location=file:/etc/cas/services
>>> cas.serviceRegistry.initFromJson=true
>>>
>>>
>>> to cas.properties and put the everything-1.json into the directory 
>>> /etc/cas/services
>>>
>>> Problem is the same :
>>>
>>> 2019-11-05 16:34:51,426 INFO [org.apereo.cas.services.
>>> AbstractServicesManager] - <Loaded [0] service(s) from [
>>> InMemoryServiceRegistry].>
>>>
>>>
>>> -- 
>>>
>>>
>>> Ray Bon
>>> Programmer Analyst
>>> Development Services, University Systems
>>> 2507218831 | CLE 019 | [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.
>>>
>>> -- 
>>>
>>> Ray Bon
>>> Programmer Analyst
>>> Development Services, University Systems
>>> 2507218831 | CLE 019 | [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/437052b9-5c8f-4d64-aa73-274bd71cb38a%40apereo.org.

Reply via email to