I had to copy the entire bootstrap.properties file over before it would 
read the external cas.properties. Unsure as to why but it took a solid day 
of fail to figure it out. The docs made it seem like just those lines were 
needed.

Here is mine that works for reference.

##
# CAS Spring Cloud Config Client
#
# Name of the application for which environment settings and properties 
should be fetched.
# This should map to a cas.yml or cas.properties file.
spring.application.name=cas
spring.cloud.config.fail-fast=false

## 
# CAS Embedded Cloud Config Server
#
# Native profile in the Config Server that doesn't use Git, but just loads 
the 
# config files from the local classpath or file system.
#
spring.profiles.active=native
spring.cloud.config.server.native.searchLocations=file://${catalina.home}/config/
# To load more they need to be named applucation-profile1.properties
# spring.profiles.include=profile1,profile2

# spring.profiles.active=default
# spring.cloud.config.server.git.uri=https://github.com/repoName/config
# spring.cloud.config.server.git.uri=file://${user.home}/config
# spring.cloud.config.server.git.username=
# spring.cloud.config.server.git.password=
spring.cloud.config.server.bootstrap=true
spring.cloud.config.server.prefix=/configserver
spring.jmx.default-domain=server

On Saturday, January 14, 2017 at 6:28:58 PM UTC-5, ray.walker wrote:
>
> In a CAS 5.0.1 Maven overlay I have the following files included:
>
>  
>
> src/main/resources/bootstrap.properties 
>
> spring.profiles.active=native
>
>
> spring.cloud.config.server.native.searchLocations=file:///nau/local/cas/config
>
>  
>
>  
>
> In the config file:
>
> /nau/local/cas/config
>
> I have some basic stuff, but it doesn’t seem to apply, such as: 
>
> cas.authn.accept.users=
>
>  
>
> In addition I have all appropriate LDAP & DUO configs set, such as:
>
> cas.authn.mfa.duo.duoApiHost=(my duo api host)
>
>  
>
> (I also have LDAP auth & Duo enabled in the pom.xml)
>
>  
>
> Upon startup I get a failed deployment:
>
>  
>
>  
>
> 14-Jan-2017 16:12:20.595 INFO [localhost-startStop-1] 
> org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned 
> for TLDs yet contained no TLDs. Enable debug logging for this logger for a 
> complete list of JARs that were scanned but no TLDs were found in them. 
> Skipping unneeded JARs during scanning can improve startup time and JSP 
> compilation time.
>
>   __  ____     _     ____  __  
>
>  / / / ___|   / \   / ___| \ \ 
>
> | | | |      / _ \  \___ \  | |
>
> | | | |___  / ___ \  ___) | | |
>
> | |  \____|/_/   \_\|____/  | |
>
>  \_\                       /_/ 
>
>  
>
> CAS Version: 5.0.1
>
> Build Date/Time: 2017-01-14T20:34:50Z
>
> System Temp Directory: /nau/local/cas/tomcat/temp
>
> Java Home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64/jre
>
> Java Vendor: Oracle Corporation
>
> Java Version: 1.8.0_111
>
> JCE Installed: yes
>
> OS Architecture: amd64
>
> OS Name: Linux
>
> OS Version: 2.6.32-642.11.1.el6.x86_64
>
>  
>
> 2017-01-14 16:12:27,985 INFO 
> [org.apereo.cas.web.CasWebApplicationServletInitializer] - <The following 
> profiles are active: native>
>
> 2017-01-14 16:12:38,726 WARN 
> [org.apereo.cas.services.InMemoryServiceRegistryDaoImpl] - <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.>
>
> 2017-01-14 16:12:38,789 INFO 
> [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 0 services 
> from InMemoryServiceRegistryDaoImpl.>
>
> 2017-01-14 16:12:44,910 WARN 
> [org.apereo.cas.config.CasSecurityContextConfiguration] - <>
>
> 2017-01-14 16:12:44,918 WARN 
> [org.apereo.cas.config.CasSecurityContextConfiguration] - <
>
>  ____   _____   ___   ____   _ 
>
> / ___| |_   _| / _ \ |  _ \ | |
>
> \___ \   | |  | | | || |_) || |
>
>  ___) |  | |  | |_| ||  __/ |_|
>
> |____/   |_|   \___/ |_|    (_)
>
>                                
>
> 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. 
>
> > 
>
> 2017-01-14 16:12:44,920 WARN 
> [org.apereo.cas.config.CasSecurityContextConfiguration] - <>
>
> 2017-01-14 16:12:52,014 INFO 
> [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 2 services 
> from InMemoryServiceRegistryDaoImpl.>
>
> 2017-01-14 16:13:00,245 INFO 
> [org.apereo.cas.configuration.CasConfigurationRebinder] - <Reloaded CAS 
> configuration cas-org.apereo.cas.configuration.CasConfigurationProperties>
>
> 2017-01-14 16:13:02,991 INFO [org.apereo.cas.configuration.support.Beans] 
> - <Ticket registry encryption/signing is turned off. This MAY NOT be safe 
> in a clustered production environment. Consider using other choices to 
> handle encryption, signing and verification of ticket registry tickets, and 
> verify the chosen ticket registry does support this behavior.>
>
> 2017-01-14 16:13:03,007 WARN 
> [org.apereo.cas.ticket.registry.DefaultTicketRegistry] - <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.>
>
> 2017-01-14 16:13:03,022 INFO 
> [org.apereo.cas.config.CasCoreTicketsConfiguration] - <Protocol tickets 
> generated by CAS are not signed/encrypted.>
>
> 2017-01-14 16:13:03,203 WARN 
> [org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext]
>  
> - <Exception encountered during context initialization - cancelling refresh 
> attempt: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 'scopedTarget.duoApiAuthenticationService': 
> Invocation of init method failed; nested exception is 
> java.lang.IllegalArgumentException: Duo API host cannot be blank>
>
> 14-Jan-2017 16:13:03.243 SEVERE [localhost-startStop-1] 
> org.apache.catalina.core.ContainerBase.addChildInternal 
> ContainerBase.addChild: start: 
>
>  org.apache.catalina.LifecycleException: Failed to start component 
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cas]]
>
>                 at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
>
>                 at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
>
>                 at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
>
>                 at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
>
>                 at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
>
>  
>
>  
>
> ...any ideas as to why cas.properties is being ignored?
>
> — 
>
> Raymond Walker
> Software Systems Engineer StSp.
> ITS Northern Arizona University
>
>  
>

-- 
- 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/52865deb-8555-4279-b173-6c94e83b22b1%40apereo.org.

Reply via email to