Ah, ok yea, I missed two of the properties. Progress! Thank you for all your help. I certainly appreciate it.
I've got the web app started and the service registry setup in cas. But I still can't get into it because of certificate issues, specifically my self signed cert is for 127.0.0.1 and not localhost. *sigh* Certs are fun. @misagh I've read those a couple times. I'm not sure what I'm supposed to make of them. I fiddled with the overlay initializer, I remember you demonstrating it at Open Apereo, but it wasn't letting me set any setting so I quickly became a dead end for me. On Tuesday, July 11, 2017 at 4:55:13 PM UTC-5, richard.frovarp wrote: > > On 07/11/2017 03:14 PM, Toby Archer wrote: > > Hmm. I assume the management app can be spung up with out having to spin > up cas right? The documentation doesn't explain how the two are connected, > but I'm guessing it has something to do with this statement: > > The persistence storage >> <https://apereo.github.io/cas/5.1.x/installation/Service-Management.html> >> for services *MUST* be the same as that of the CAS server. >> > > Further this statement: > > The service management webapp is a standalone web application that may be >> deployed along side CAS >> > > leads me to assume that the management app can be deployed on a separate > server entirely. So I decided to fiddle around with just getting the > management app up and running, and deal with connecting next. I build it, > that went fine. but when I try to run it I get: jasigcas.herokuapp.com so > the app it'self doesn't appear to be running? Am I missing something? > > > The management app is a web application that uses CAS to provide its > authentication services. So you need a CAS server to provide authentication > services to the management application. Generally you would have them > paired up, but I have had them split in the past. You do need them to point > at the same persistence storage, which in the case of DB / JPA is just > doing those settings. > > That looks like it probably worked. I'm guessing that value is the default > setting from the overlay that you need to override so that it points to > your CAS instead of the demo one. Documentation seems to be missing a > setting or two. My config has the two cas.server.name and prefix values > set to point to the CAS server. This is what tells the management > application where to send the user to authenticate. I've also had to set > the cas.mgmt.serverName and server.contextPath values to make things work. > But I am moving this around a bit and may not impact you. I need to get to > where I'm running three sets of CAS applications (server + management) out > of the same Tomcat instance. > > > https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#cas-server > > cas.server.name=https://wings.it.ndsu.edu > cas.server.prefix=${cas.server.name}/cas > cas.mgmt.serverName=https://wings.it.ndsu.edu > server.contextPath=/cas-management-ndsu > > > -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- 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/fd8668bc-c165-44a9-8b21-e3cdc15b26e2%40apereo.org.
