Im new to CAS, and im trying to run CAS locally on windows, using the war overlay. I've tried both maven and gradle overlay, "build package" command done successfully, but the "build run" command stuck on the same place. no error, process still running, only stuck. Both maven and gradle overlay stuck on the same place. Here is the couple last lines of logs:
__ ____ _ ____ __
/ / / ___| / \ / ___| \ \
| | | | / _ \ \___ \ | |
| | | |___ / ___ \ ___) | | |
| | \____| /_/ \_\ |____/ | |
\_\ /_/
CAS Version: 5.2.1
CAS Commit Id: c8106bf0a3309df1a1fb0a6cbe935b5a4e557431
CAS Build Date/Time: 2018-01-16T04:15:11.079Z
Spring Boot Version: 1.5.8.RELEASE
------------------------------------------------------------
Java Home: C:\Program Files\Java\jdk1.8.0_112\jre
Java Vendor: Oracle Corporation
Java Version: 1.8.0_112
JVM Free Memory: 202 MB
JVM Maximum Memory: 1 GB
JVM Total Memory: 733 MB
JCE Installed: No
------------------------------------------------------------
OS Architecture: amd64
OS Name: Windows 10
OS Version: 10.0
OS Date/Time: 2018-01-16T11:15:21.930
OS Temp Directory: C:\Users\***\Temp\
------------------------------------------------------------
Apache Tomcat Version: Apache Tomcat/8.5.24
------------------------------------------------------------
2018-01-16 11:15:22,005 INFO [org.apereo.cas.configuration.config.CasCoreBootstrapStandaloneConfiguration] - <Configuration files found at [\etc\cas\config] are [[\etc\cas\config\application.yml, \etc\cas\config\cas.properties]]>
2018-01-16 11:15:22,037 INFO [org.apereo.cas.configuration.config.CasCoreBootstrapStandaloneConfiguration] - <Found and loaded [5] setting(s) from [\etc\cas\config]>
2018-01-16 11:15:22,038 INFO [org.springframework.cloud.bootstrap.config.PropertySourceBootstrapConfiguration] - <Located property source: PropertiesPropertySource {name='standaloneCasConfigService'}>
2018-01-16 11:15:26,922 WARN [org.apereo.cas.config.CasCoreTicketsConfiguration] - <Runtime memory is used as the persistence storage for retrieving and managing tickets. Tickets that are issued during runtime will be LOST upon container restarts. This MAY impact SSO functionality.>
2018-01-16 11:15:39,112 WARN [org.apereo.cas.config.support.authentication.AcceptUsersAuthenticationEventExecutionPlanConfiguration] - <>
2018-01-16 11:15:39,115 WARN [org.apereo.cas.config.support.authentication.AcceptUsersAuthenticationEventExecutionPlanConfiguration] - <
____ _____ ___ ____ _
/ ___| |_ _| / _ \ | _ \ | |
\___ \ | | | | | | | |_) | | |
___) | | | | |_| | | __/ |_|
|____/ |_| \___/ |_| (_)
CAS is configured to accept a static list of credentials for authentication. While this is generally useful for demo purposes, it is STRONGLY recommended that you DISABLE this authentication method (by setting 'cas.authn.accept.users' to a blank value) and switch to a mode that is more suitable for production.>
2018-01-16 11:15:39,116 WARN [org.apereo.cas.config.support.authentication.AcceptUsersAuthenticationEventExecutionPlanConfiguration] - <>
2018-01-16 11:15:53,189 WARN [org.apereo.cas.config.CasCoreServicesConfiguration] - <Runtime memory is used as the persistence storage for retrieving and persisting service definitions. Changes that are made to service definitions during runtime WILL be LOST upon container restarts. Ideally for production, you need to choose a storage option (JDBC, etc) to store and track service definitions.>
2018-01-16 11:15:53,660 WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Secret key for encryption is not defined for [Ticket-granting Cookie]; CAS will attempt to auto-generate the encryption key>
2018-01-16 11:15:53,673 WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated encryption key [9oh7md1kNgyucCCITTB5vxTBiPuo7IhPgMaEDKM6Z6U] of size [256] for [Ticket-granting Cookie]. The generated key MUST be added to CAS settings under setting [cas.tgc.crypto.encryption.key].>
2018-01-16 11:15:53,676 WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Secret key for signing is not defined for [Ticket-granting Cookie]. CAS will attempt to auto-generate the signing key>
2018-01-16 11:15:53,677 WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated signing key [zQAXq29Zukb8aY_zNlJjwAMddhEa9kDuHeZoU95Ztf3RJSELuV-UUojWAok8O7WS_lyDsqAlYf478YhARP6AhA] of size [512] for [Ticket-granting Cookie]. The generated key MUST be added to CAS settings under setting [cas.tgc.crypto.signing.key].>
2018-01-16 11:15:54,154 WARN [org.apereo.cas.util.cipher.BaseBinaryCipherExecutor] - <Secret key for signing is not defined under [cas.webflow.crypto.signing.key]. CAS will attempt to auto-generate the signing key>
2018-01-16 11:15:54,154 WARN [org.apereo.cas.util.cipher.BaseBinaryCipherExecutor] - <Generated signing key [Zu_gse4yMGMXoWT7ei9eY2RRhLkerZo7oKhgPCcK2GI_xfScX3feC-s5kXWXmX1b2nNH3rFWF5qkleM9EwO43A] of size [512]. The generated key MUST be added to CAS settings under setting [cas.webflow.crypto.signing.key].>
2018-01-16 11:15:54,154 WARN [org.apereo.cas.util.cipher.BaseBinaryCipherExecutor] - <Secret key for encryption is not defined under [cas.webflow.crypto.encryption.key]. CAS will attempt to auto-generate the encryption key>
2018-01-16 11:15:54,160 WARN [org.apereo.cas.util.cipher.BaseBinaryCipherExecutor] - <Generated encryption key [biaqOHU0fJ6RkiGWe29iqw] of size [16]. The generated key MUST be added to CAS settings under setting [cas.webflow.crypto.encryption.key].>
After that, there is no further progress or any errors or anything. Ive tried waiting for about 1 hour with no progress or "FINISHED" state. Anybody has same experience or solution for this?
Thanks for any help and sorry for my stupid english.
Regards.