In our development environments, we are attempting to get cas-management implemented. We have attempted the management-overlay 6.1 and 6.3. We have also jerry rigged 6.2.2 using the 6.1 overlay.
We keep running into two showstopper issues: 1. "Return Allowed" attribute release interface does not load the attributes list in the drop down. This seems to be present in 6.1 and 6.3, but works in 6.2.2. 2. The second is the local git repository seems to throw an exception in 6.2.2. This exception is tied to org.apereo.cas.mgmt.controller.CommitController.isPublishedBehind(CommitController.java:199) ~[cas-mgmt-support-version-control-6.2.2.jar:6.2.2] From, what I can gather it seems that controller is assuming one repo per environment and it searching for uncommitted changes to the repo. We are running separate branches for each environment, and this seems to be acceptable in CAS server, but not CAS-MANAGEMENT. Does anyone have any insights into these problems? -- - 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/b968952e097a4d4387c34d57f0598685%40mun.ca.
