Thank you Frédéri. I've been playing around and I ran curl -k https://getcas.apereo.org/starter.tgz \ -d type=cas-overlay -d baseDir=overlay | tar -xzvf -
This made an overview file that had SAML and Services folder in the /etc/cas. However there is still no keystore. I've tried running your command among "./gradlew.bat createkeystore --info" and it keeps erroring. I get Custom actions are attached to task ':createKeystore'. Caching disabled for task ':createKeystore' because: Gradle would require more information to cache this task Task ':createKeystore' is not up-to-date because: Task has not declared any outputs despite executing actions. I've tried running it out of gradlew with your command and it doesn't seem to recognize keytool despite my environmental variables being java_21 and the bin folder has the ./keytool.exe On Wed, Jul 3, 2024 at 8:08 AM Frédéric Dussurget <dussurg...@gmail.com> wrote: > Hi Benjamin, > > as saml and services folders are not mandatory (saml is optionnal and you > may store your services elsewhere, eg. in a mongo/redit/postgres db ...) > you'll have to handle this on your own > You might write your cas.properties file from scratch (know that cas > properties could also be stored in a .yml format ...) > > If you choose your filesystem to store services, create the folder > /etc/cas/services regarding the documentation you've just told about : > cas.service-registry.core.init-from-json=false > cas.service-registry.json.location=file:/etc/cas/services > > Same thing for SAML. > > Finally, about Keystore, the doc says : > By default, the CAS web application expects to run on the secure port 8443 > which requires that you create a keystore file at /etc/cas/ named > thekeystore. > > So, let's generate your own keystore with keytool, eg : > sudo keytool -keystore /etc/cas/thekeystore -keyalg RSA -genkey -alias > shared > sudo keytool -importkeystore -srckeystore mywonderful.p12 -destkeystore > /etc/cas/thekeystore -srcstoretype pkcs12 -alias shared > > (Watch for permissions on every file/folder you create so that your tomcat > webapp can open them) > > hope it helps > Le mardi 2 juillet 2024 à 17:49:20 UTC+2, Ben a écrit : > >> Hello, >> >> >> >> I am trying to generate a deployment of CAS 7.0. From reading the >> documentation, I should (and am hopefully) using a clean WAR Overlay build. >> I am using guides I found in the CAS Community such as the following: >> >> - >> >> https://paulchauvet.github.io/deploying-cas/building-cas/initial-cas-config/ >> - https://fawnoos.com/2023/12/15/cas70x-gettingstarted-overlay/ >> >> >> >> I am going the route of checking out (and creating my own branch of) >> branch 7.0 from https://github.com/apereo/cas-overlay-template/tree/7.0 >> instead of doing the curl command. I then run the “./gradlew clean build” >> command. That works. Next, from all the documentation, it mentions to look >> into the cas.properties files among others. When I look into the etc/config >> folder, I seem to be missing many files like the SAML and Services folder, >> and the keystore. Having missing SAML and Services folders causes my builds >> to fail too. >> >> >> >> How does one generate the files (among others I’m sure I’m missing)? Am I >> missing an obvious step? >> >> >> >> Thanks, >> >> Benjamin Chang >> > -- - 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/CAKZ%3Dx12yMsAh4-4KqNWrrOZzdcZU8O3A%3D8h_uiFwOu4JNpJYOQ%40mail.gmail.com.
