CAS Spring Boot Administration

CAS takes advantage of Spring Boot Admin to manage and monitor its internal state visually. As a Spring Boot Admin client, CAS registers itself with the Spring Boot Admin server over HTTP and reports back its status and health to the server’s web interface.

Spring Boot Admin Server

The Spring Boot Admin web application server is part of the CAS server via a dedicated extension module. Support is added by including the following dependency in the WAR overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-bootadmin</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-bootadmin:${project.'cas.version'}"

dependencyManagement {
    imports {
        mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
    }
}

dependencies {
    implementation "org.apereo.cas:cas-server-support-bootadmin"
}

dependencies {
    /*
    The following platform references should be included automatically and are listed here for reference only.
            
    implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
    implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
    */

    implementation "org.apereo.cas:cas-server-support-bootadmin"
}

Secure Endpoints

Note that the admin server's API endpoints MUST be secured. It is also best to run both the Admin server and the registering CAS server node under HTTPS, specially if credentials are used to authenticate into endpoints.

Once deployed, the Spring Boot Admin dashboard is available under the /sba context path.

To learn more about options, please see this guide.

The following settings and properties are available from the CAS configuration catalog:

_{The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.}

_{The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. In other words, you should only include this field in your
configuration if you need to modify the default value or if you need to turn on the feature controlled by the setting.}

_{The configuration settings listed below are tagged as Third Party in the CAS configuration metadata. This flag indicates that the configuration setting is not controlled, owned or managed by the CAS ecosystem, and affects functionality that is offered by a third-party library, such as Spring Boot or Spring Cloud to CAS. For additional info, you might have to visit the third-party source to find more details.}

spring.boot.admin.server.enabled=true

Enable Spring Boot Admin Server Default: true

de.codecentric.boot.admin.server.config.AdminServerProperties$ServerProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.server.enabled=true

This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework.

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      server: 
        enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.server.enabled="true" -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. Note the placement of the system property which must be specified before the CAS web application is launched.

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_SERVER_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.server.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Configuration Metadata

The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.

Be Selective

This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.

YAGNI

Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.

Naming Convention

Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those that might be presented to the system via an external library or framework such as Spring Boot, etc.

Note

Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the way you intend.

Validation

Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.

Indexed Settings

CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be incremented by the adopter to allow for distinct multiple configuration blocks.

Spring Boot Admin Client

Each individual CAS server is given the ability to auto-register itself with the Spring Boot Admin server, provided configuration is made available to instruct the CAS server how to locate and connect to the admin server.

Note that CAS server’s actuator endpoints are by default secured. In order to allow secure communication between the CAS server and the Spring Boot Admin server, please see guide.

The following settings and properties are available from the CAS configuration catalog:

spring.boot.admin.client.api-path=instances

The admin rest-apis path.

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.api-path=instances

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        api-path: "instances"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.api-path="instances" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_API_PATH="instances"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.api-path="instances"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.auto-deregistration=

Enable automatic deregistration on shutdown If not set it defaults to true if a active CloudPlatform is present;

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.auto-deregistration=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        auto-deregistration: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.auto-deregistration="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_AUTO_DEREGISTRATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.auto-deregistration="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.auto-registration=true

Enable automatic registration when the application is ready.

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.auto-registration=true

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        auto-registration: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.auto-registration="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_AUTO_REGISTRATION="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.auto-registration="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.connect-timeout=5000ms

Connect timeout for the registration.

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.connect-timeout=5000ms

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        connect-timeout: "5000ms"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.connect-timeout="5000ms" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_CONNECT_TIMEOUT="5000ms"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.connect-timeout="5000ms"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.enabled=true

Enable Spring Admin Client.

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.health-url=

Client-health-URL to register with. Inferred at runtime, can be overridden in case the reachable URL is different (e.g. Docker). Must be unique all services registry.

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.health-url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          health-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.health-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_HEALTH_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.health-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.management-base-url=

Base url for computing the management-url to register with. The path is inferred at runtime, and appended to the base url.

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.management-base-url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          management-base-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.management-base-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_MANAGEMENT_BASE_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.management-base-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.management-url=

Management-url to register with. Inferred at runtime, can be overridden in case the reachable URL is different (e.g. Docker).

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.management-url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          management-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.management-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_MANAGEMENT_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.management-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.metadata=

Metadata that should be associated with this application

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.metadata=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          metadata: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.metadata="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_METADATA="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.metadata="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.name=spring-boot-application

Name to register with. Defaults to ${spring.application.name}

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.name=spring-boot-application

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          name: "spring-boot-application"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.name="spring-boot-application" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_NAME="spring-boot-application"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.name="spring-boot-application"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.prefer-ip=false

Should the registered urls be built with server.address or with hostname. Deprecation: Use serviceHostType instead.

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.prefer-ip=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          prefer-ip: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.prefer-ip="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_PREFER_IP="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.prefer-ip="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is WARNINGwithout a replacement setting.

spring.boot.admin.client.instance.service-base-url=

Base url for computing the service-url to register with. The path is inferred at runtime, and appended to the base url.

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.service-base-url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          service-base-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.service-base-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_SERVICE_BASE_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.service-base-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.service-host-type=

Should the registered urls be built with server.address or with hostname.

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.service-host-type=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          service-host-type: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.service-host-type="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_SERVICE_HOST_TYPE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.service-host-type="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.service-path=

Path for computing the service-url to register with. If not specified, defaults to "/"

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.service-path=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          service-path: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.service-path="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_SERVICE_PATH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.service-path="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.instance.service-url=

Client-service-URL register with. Inferred at runtime, can be overridden in case the reachable URL is different (e.g. Docker).

de.codecentric.boot.admin.client.config.InstanceProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.instance.service-url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        instance: 
          service-url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.instance.service-url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_INSTANCE_SERVICE_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.instance.service-url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.password=

Password for basic authentication on admin server

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.period=10000ms

Time interval the registration is repeated

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.period=10000ms

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        period: "10000ms"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.period="10000ms" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_PERIOD="10000ms"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.period="10000ms"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.read-timeout=5000ms

Read timeout (in ms) for the registration.

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.read-timeout=5000ms

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        read-timeout: "5000ms"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.read-timeout="5000ms" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_READ_TIMEOUT="5000ms"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.read-timeout="5000ms"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.register-once=true

Enable registration against one or all admin servers

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.register-once=true

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        register-once: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.register-once="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_REGISTER_ONCE="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.register-once="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.url=

The admin server urls to register at

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.url=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.boot.admin.client.username=

Username for basic authentication on admin server

de.codecentric.boot.admin.client.config.ClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.boot.admin.client.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  boot: 
    admin: 
      client: 
        username: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.boot.admin.client.username="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_BOOT_ADMIN_CLIENT_USERNAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.boot.admin.client.username="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

# The admin rest-apis path.
# spring.boot.admin.client.api-path=instances

# Enable automatic deregistration on shutdown If not set it defaults to true if a active {@link CloudPlatform} is present;
# spring.boot.admin.client.auto-deregistration=

# Enable automatic registration when the application is ready.
# spring.boot.admin.client.auto-registration=true

# Connect timeout for the registration.
# spring.boot.admin.client.connect-timeout=5000ms

# Enable Spring Admin Client.
# spring.boot.admin.client.enabled=true

# Client-health-URL to register with.
# spring.boot.admin.client.instance.health-url=

# Base url for computing the management-url to register with.
# spring.boot.admin.client.instance.management-base-url=

# Management-url to register with.
# spring.boot.admin.client.instance.management-url=

# Metadata that should be associated with this application
# spring.boot.admin.client.instance.metadata=

# Name to register with.
# spring.boot.admin.client.instance.name=spring-boot-application

# Should the registered urls be built with server.address or with hostname.
# spring.boot.admin.client.instance.prefer-ip=false

# Base url for computing the service-url to register with.
# spring.boot.admin.client.instance.service-base-url=

# Should the registered urls be built with server.address or with hostname.
# spring.boot.admin.client.instance.service-host-type=

# Path for computing the service-url to register with.
# spring.boot.admin.client.instance.service-path=

# Client-service-URL register with.
# spring.boot.admin.client.instance.service-url=

# Password for basic authentication on admin server
# spring.boot.admin.client.password=

# Time interval the registration is repeated
# spring.boot.admin.client.period=10000ms

# Read timeout (in ms) for the registration.
# spring.boot.admin.client.read-timeout=5000ms

# Enable registration against one or all admin servers
# spring.boot.admin.client.register-once=true

# The admin server urls to register at
# spring.boot.admin.client.url=[0]

# Username for basic authentication on admin server
# spring.boot.admin.client.username=

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Security

Accessing the Spring Boot Admin Server will by default require a form-based user authentication. The credentials used to access this feature are those presented by Spring Security configuration:

The following settings and properties are available from the CAS configuration catalog:

spring.security.user.name=user

Default user name.

org.springframework.boot.autoconfigure.security.SecurityProperties$User.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.security.user.name=user

CAS properties can be specified using the YAML syntax:

spring: 
  security: 
    user: 
      name: "user"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.security.user.name="user" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_SECURITY_USER_NAME="user"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.security.user.name="user"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.security.user.password=

Password for the default user name.

org.springframework.boot.autoconfigure.security.SecurityProperties$User.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.security.user.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  security: 
    user: 
      password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.security.user.password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_SECURITY_USER_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.security.user.password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.security.user.roles=

Granted roles for the default user name.

org.springframework.boot.autoconfigure.security.SecurityProperties$User.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.security.user.roles=...

CAS properties can be specified using the YAML syntax:

spring: 
  security: 
    user: 
      roles: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.security.user.roles="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_SECURITY_USER_ROLES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.security.user.roles="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Additional points to consider:

Spring Boot Admin Server will reach out to CAS actuator endpoints to parse and present data. As CAS actuator endpoints require authenticated access, Spring Boot Admin Server is configured by default to use the same credentials used to protected actuator endpoints.
CAS server acting as a Spring Boot Admin client will reach out to the Spring Boot Admin Server to auto-register itself and report status updates. Such requests and API calls re by default configured to use the same security mechanism and credentials.
CAS server can act both as a Spring Boot Admin Server or a client of the Spring Boot Admin Server. Each CAS server deployment can be individually tuned to turn off client/service functionality as needed. For example, in a clustered CAS deployment the primary CAS server node might act as both Spring Boot Admin Server and Client, while all other secondary nodes may simply be a client of the primary CAS (Spring Boot Admin) server.

Troubleshooting

To enable additional logging, modify the logging configuration file to add the following:

<Logger name="de.codecentric.boot" level="debug" />
<Logger name="org.springframework.web.reactive" level="debug" />