Sorry to also chime in on an old thread but I've just been trying to upgrade to the latest cas-management overlay today and ran into similar issues.
For the issue where *existing* services weren't showing up it might be incorrect permissions on the git repo that is automatically generated in the mgmt.versionControl.servicesRepo path. If I recall several items under .git had bad permission preventing the tomcat service from reading the repo (e.g. .git/index, .git/config) and a chown tomcat: -R .git fixed it after a service restart. On Thursday, March 26, 2020 at 11:02:19 AM UTC-7, JC wrote: > > I know this topic is five months old, but I wanted to add what I > discovered so that it will be here if someone else finds this in a search, > like I did. > > I have found that the documentation that shows the two properties' syntax > referenced is wrong, unsurprisingly. The values that worked for me in the > 6.1.5 management web app are: > > mgmt.versionControl.enabled=false > mgmt.delegated.enabled=false > > However, even with version control disabled, the management app *still* > wants to put stuff in '/etc/cas/services-repo'. The following property > changes that: > > mgmt.versionControl.servicesRepo=file:/path/to/services > > Now the management app saves *new *services in the directory I want, but > doesn't show existing services. This whole version control thing is a real > pain. > > J > -- - 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/f5efb6b6-40de-4640-a359-7fffd462c09eo%40apereo.org.
