Re: [cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

I noticed that if I set cas.serviceRegistry.initFromJson to false, two json files are automatically created for me when CAS starts up, Apereo-1002.json and HTTPSandIMAPS-1001.json with default values. How can this be avoided? I recall this came up on the list a while back, so you might

Re: [cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

Using cas.serviceRegistry.json.location instead of cas.serviceRegistry.config.location solved my issue. Apparently this changed between 5.1.x and 5.2.0. Once again, thanks Dave for working me through this. About your second comment, I noticed that if I set cas.serviceRegistry.initFromJson

Re: [cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

You have the wrong property name (I forget when it changed). cas.serviceRegistry.json.location: file:/etc/cas/services Also, since you have your own non-empty service registry, you should have cas.serviceRegistry.initFromJson: false That property tells the CAS server to load an otherwise

[cas-user] JSON Service Registry cas.serviceRegistry.config.location property setting ineffective after upgrading to CAS version 5.2

I updated my test sever from CAS v5.1.4 to v5.2.0, and my configruation is no longer reading my *.json files from my external file location. Here are my relevant property settings: # # Service Registry #