Previously configured and have been running CAS 6.6 in production for a while.
Recently looking to upgrade to CAS 7.0.
Able to build and run 7.0, but it will only listen on 127.0.0.1 regardless of all efforts otherwise.
have tried the following with cas.properties,
server.address=x.x.x.x
have also tried setting this in *.yaml, -Dserver.port=, etc.
Have spent hours comparing settings against those for 6.6, reading the docs on apereo cas site, fawnoos, and anything else I can find.
Guessing this is something obvious that I am missing, but has anyone else run into this, and if so how did you solve it?
It WILL correctly set the port using server.port=xxxx,
but using the following ==> lsof -i -P -n | grep LISTEN
CAS 7.0 shows it is only listening on 127.0.0.1:xxxx,
CAS 6.6 deployment will show =*.xxxx
On startup it DOES show the correct server name, finding configuration files, etc.
CAS Version: 7.0.0
CAS Branch: 7.0.x
CAS Commit Id: b1e65f89a4854e3690b68a52b0589ecbbbb1eb3f
CAS Build Date/Time: 2023-12-29T10:06:15.981035Z
Spring Boot Version: 3.2.1
Spring Version: 6.1.2
Java Home: /usr/local/zulu21.32.17-ca-jdk21.0.2-linux_x64
Java Vendor: Azul Systems, Inc.
Java Version: 21.0.2
Servlet Version: 6.0.0
JVM Free Memory: 73 MB
JVM Maximum Memory: 2 GB
JVM Total Memory: 247 MB
OS Architecture: amd64
OS Name: Linux
OS Version: 4.19.0-24-amd64
OS Date/Time: 2024-01-25T15:00:09.617932208
OS Temp Directory: /tmp
------------------------------------------------------------
Apache Tomcat Version: Apache Tomcat/10.1.17
------------------------------------------------------------
...
2024-01-25 15:00:09,715 INFO [org.apereo.cas.configuration.DefaultCasConfigurationPropertiesSourceLocator] - <Configuration files found at [<expected config file location>] are [[file [<expected config file location>/cas.properties]]] under profile(s) [[standalone]]>
...
CAS is now running at https://<the domain>/auth