Morning, https://github.com/Unicon/cas-addons/wiki/Configuring-JSON-Service-Registry
> Note: Since version 1.9, the value of the config-file attribute does not have > to be file > but rather, could be an external URL publicly available. What is the behavior when watching a URL here (running server, not during startup) and the source happens to be down for a "while" (TBD)? Does CAS (3.6) keep using what's cached (presumably in memory)? Until when? I didn't see this offhand, but does/can CAS locally persist service registry data fetched from a URL (e.g. similar to Shibboleth)? Across restarts? Or would that require e.g. JPA? I'm trying to balance trade offs of the various mechanisms built into this version CAS vs. deploying service registry data by some other (configuration management) means. FWIW, we're actively pursuing CAS 4.x, though may need to deploy 3.6 as an intermediate step to accomplish some short-term business goals. Thanks! Tom. -- 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]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
