SAML SP Integrations

CAS provides built-in integration support for a number of SAML2 service providers. Configuring these service providers is about declaring the relevant properties in the CAS configuration as well as the configuration module below. Each integration, when configured appropriately, will register the service provider with the CAS service registry as a SAML SP and will follow a recipe (that is documented by the SP publicly) to configure attribute release policies, name ids and entity IDs. If you need to, you can review the registration record inside the CAS service registry to adjust options.

NOTE: In the event that special attributes and/or name ids are required for the integration, you are required to ensure all such attributes are properly resolved and are available to the CAS principal.

Remember

SAML2 service provider integrations listed here attempt to automate CAS configuration based on known and documented integration guidelines and recipes provided by the service provider owned by the vendor. These recipes can change and break CAS over time and needless to say, they need to be properly and thoroughly tested as the project itself does not have a subscription to each application to test for correctness. YMMV. If you find an issue with an automated integration strategy here, please speak up.

Support is enabled by including the following module in the WAR Overlay:

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

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

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

dependencies {
    implementation "org.apereo.cas:cas-server-support-saml-sp-integrations"
}

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-saml-sp-integrations"
}

The following SAML SP integrations, as samples, are provided by CAS:

Configure Once, Run Everywhere

If you have developed a recipe for integrating with a SAML service provider, consider contributing that recipe to the project so its configuration can be automated once and for all to use. Let the change become a feature of the project, rather than something you alone have to maintain.

Configuration

Allow CAS to register and enable a number of built-in SAML service provider integrations.

Remember

The settings defined for each service provider attempt to automate the creation of SAML service definition and nothing more. If you find the applicable settings lack in certain areas, it is best to fall back onto the native configuration strategy for registering SAML service providers with CAS which would depend on your service registry of choice.

The SAML2 service provider supports the following settings:

Name	Description
`metadata`	Location of metadata for the service provider (i.e URL, path, etc)
`name`	The name of the service provider registered in the service registry.
`description`	The description of the service provider registered in the service registry.
`name-id-attribute`	Attribute to use when generating name ids for this service provider.
`name-id-format`	The forced NameID Format identifier (i.e. `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`).
`attributes`	Attributes to release to the service provider, which may virtually be mapped and renamed.
`signature-location`	Signature location to verify metadata.
`entity-ids`	List of entity ids allowed for this service provider.
`sign-responses`	Indicate whether responses should be signed. Default is `true`.
`sign-assertions`	Indicate whether assertions should be signed. Default is `false`.

The only required setting that would activate the automatic configuration for a service provider is the presence and definition of metadata. All other settings are optional.

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.}

cas.saml-sp.academic-health-plans.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.metadata=...

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:

cas: 
  saml-sp: 
    academic-health-plans: 
      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 -Dcas.saml-sp.academic-health-plans.metadata="..." -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 CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_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 --cas.saml-sp.academic-health-plans.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.

cas.saml-sp.adobe-cloud.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      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 -Dcas.saml-sp.adobe-cloud.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_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 --cas.saml-sp.adobe-cloud.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.

cas.saml-sp.amazon.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      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 -Dcas.saml-sp.amazon.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_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 --cas.saml-sp.amazon.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.

cas.saml-sp.app-dynamics.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      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 -Dcas.saml-sp.app-dynamics.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_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 --cas.saml-sp.app-dynamics.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.

cas.saml-sp.arc-g-i-s.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.ArcGIS.

_{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:

cas.saml-sp.arc-g-i-s.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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 -Dcas.saml-sp.arc-g-i-s.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ARC_G_I_S_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 --cas.saml-sp.arc-g-i-s.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.

cas.saml-sp.arms-software.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.ArmsSoftware.

_{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:

cas.saml-sp.arms-software.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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 -Dcas.saml-sp.arms-software.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ARMS_SOFTWARE_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 --cas.saml-sp.arms-software.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.

cas.saml-sp.asana.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Asana.

_{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:

cas.saml-sp.asana.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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 -Dcas.saml-sp.asana.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ASANA_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 --cas.saml-sp.asana.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.

cas.saml-sp.benefit-focus.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.BenefitFocus.

_{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:

cas.saml-sp.benefit-focus.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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 -Dcas.saml-sp.benefit-focus.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_BENEFIT_FOCUS_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 --cas.saml-sp.benefit-focus.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.

cas.saml-sp.black-baud.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.BlackBaud.

_{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:

cas.saml-sp.black-baud.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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 -Dcas.saml-sp.black-baud.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_BLACK_BAUD_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 --cas.saml-sp.black-baud.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.

cas.saml-sp.box.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Box.

_{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:

cas.saml-sp.box.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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 -Dcas.saml-sp.box.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_BOX_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 --cas.saml-sp.box.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.

cas.saml-sp.bynder.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Bynder.

_{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:

cas.saml-sp.bynder.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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 -Dcas.saml-sp.bynder.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_BYNDER_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 --cas.saml-sp.bynder.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.

cas.saml-sp.cccco.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.CaliforniaCommunityColleges.

_{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:

cas.saml-sp.cccco.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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 -Dcas.saml-sp.cccco.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CCCCO_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 --cas.saml-sp.cccco.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.

cas.saml-sp.cher-well.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.CherWell.

_{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:

cas.saml-sp.cher-well.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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 -Dcas.saml-sp.cher-well.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CHER_WELL_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 --cas.saml-sp.cher-well.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.

cas.saml-sp.concur-solutions.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.ConcurSolutions.

_{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:

cas.saml-sp.concur-solutions.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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 -Dcas.saml-sp.concur-solutions.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CONCUR_SOLUTIONS_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 --cas.saml-sp.concur-solutions.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.

cas.saml-sp.confluence.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Confluence.

_{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:

cas.saml-sp.confluence.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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 -Dcas.saml-sp.confluence.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CONFLUENCE_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 --cas.saml-sp.confluence.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.

cas.saml-sp.cranium-cafe.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.CraniumCafe.

_{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:

cas.saml-sp.cranium-cafe.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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 -Dcas.saml-sp.cranium-cafe.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CRANIUM_CAFE_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 --cas.saml-sp.cranium-cafe.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.

cas.saml-sp.crash-plan.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.CrashPlan.

_{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:

cas.saml-sp.crash-plan.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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 -Dcas.saml-sp.crash-plan.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_CRASH_PLAN_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 --cas.saml-sp.crash-plan.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.

cas.saml-sp.docu-sign.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.DocuSign.

_{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:

cas.saml-sp.docu-sign.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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 -Dcas.saml-sp.docu-sign.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_DOCU_SIGN_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 --cas.saml-sp.docu-sign.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.

cas.saml-sp.dropbox.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Dropbox.

_{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:

cas.saml-sp.dropbox.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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 -Dcas.saml-sp.dropbox.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_DROPBOX_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 --cas.saml-sp.dropbox.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.

cas.saml-sp.easy-iep.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.EasyIep.

_{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:

cas.saml-sp.easy-iep.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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 -Dcas.saml-sp.easy-iep.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_EASY_IEP_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 --cas.saml-sp.easy-iep.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.

cas.saml-sp.egnyte.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Egnyte.

_{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:

cas.saml-sp.egnyte.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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 -Dcas.saml-sp.egnyte.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_EGNYTE_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 --cas.saml-sp.egnyte.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.

cas.saml-sp.emma.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Emma.

_{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:

cas.saml-sp.emma.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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 -Dcas.saml-sp.emma.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_EMMA_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 --cas.saml-sp.emma.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.

cas.saml-sp.ever-bridge.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.EverBridge.

_{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:

cas.saml-sp.ever-bridge.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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 -Dcas.saml-sp.ever-bridge.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_EVER_BRIDGE_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 --cas.saml-sp.ever-bridge.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.

cas.saml-sp.evernote.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Evernote.

_{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:

cas.saml-sp.evernote.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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 -Dcas.saml-sp.evernote.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_EVERNOTE_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 --cas.saml-sp.evernote.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.

cas.saml-sp.famis.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Famis.

_{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:

cas.saml-sp.famis.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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 -Dcas.saml-sp.famis.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_FAMIS_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 --cas.saml-sp.famis.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.

cas.saml-sp.gartner.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Gartner.

_{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:

cas.saml-sp.gartner.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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 -Dcas.saml-sp.gartner.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_GARTNER_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 --cas.saml-sp.gartner.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.

cas.saml-sp.gitlab.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Gitlab.

_{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:

cas.saml-sp.gitlab.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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 -Dcas.saml-sp.gitlab.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_GITLAB_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 --cas.saml-sp.gitlab.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.

cas.saml-sp.give-campus.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.GiveCampus.

_{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:

cas.saml-sp.give-campus.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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 -Dcas.saml-sp.give-campus.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_GIVE_CAMPUS_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 --cas.saml-sp.give-campus.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.

cas.saml-sp.in-common.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.InCommon.

_{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:

cas.saml-sp.in-common.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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 -Dcas.saml-sp.in-common.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_IN_COMMON_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 --cas.saml-sp.in-common.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.

cas.saml-sp.infinite-campus.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.InfiniteCampus.

_{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:

cas.saml-sp.infinite-campus.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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 -Dcas.saml-sp.infinite-campus.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_INFINITE_CAMPUS_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 --cas.saml-sp.infinite-campus.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.

cas.saml-sp.jira.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Jira.

_{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:

cas.saml-sp.jira.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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 -Dcas.saml-sp.jira.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_JIRA_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 --cas.saml-sp.jira.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.

cas.saml-sp.neo-gov.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.NeoGov.

_{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:

cas.saml-sp.neo-gov.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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 -Dcas.saml-sp.neo-gov.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_NEO_GOV_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 --cas.saml-sp.neo-gov.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.

cas.saml-sp.net-partner.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.NetPartner.

_{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:

cas.saml-sp.net-partner.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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 -Dcas.saml-sp.net-partner.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_NET_PARTNER_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 --cas.saml-sp.net-partner.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.

cas.saml-sp.new-relic.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.NewRelic.

_{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:

cas.saml-sp.new-relic.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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 -Dcas.saml-sp.new-relic.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_NEW_RELIC_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 --cas.saml-sp.new-relic.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.

cas.saml-sp.office365.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Office365.

_{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:

cas.saml-sp.office365.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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 -Dcas.saml-sp.office365.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_OFFICE365_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 --cas.saml-sp.office365.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.

cas.saml-sp.open-athens.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.OpenAthens.

_{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:

cas.saml-sp.open-athens.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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 -Dcas.saml-sp.open-athens.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_OPEN_ATHENS_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 --cas.saml-sp.open-athens.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.

cas.saml-sp.pager-duty.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.PagerDuty.

_{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:

cas.saml-sp.pager-duty.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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 -Dcas.saml-sp.pager-duty.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_PAGER_DUTY_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 --cas.saml-sp.pager-duty.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.

cas.saml-sp.poll-everywhere.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.PollEverywhere.

_{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:

cas.saml-sp.poll-everywhere.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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 -Dcas.saml-sp.poll-everywhere.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_POLL_EVERYWHERE_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 --cas.saml-sp.poll-everywhere.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.

cas.saml-sp.qualtrics.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Qualtrics.

_{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:

cas.saml-sp.qualtrics.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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 -Dcas.saml-sp.qualtrics.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_QUALTRICS_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 --cas.saml-sp.qualtrics.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.

cas.saml-sp.rocket-chat.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.RocketChat.

_{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:

cas.saml-sp.rocket-chat.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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 -Dcas.saml-sp.rocket-chat.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ROCKET_CHAT_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 --cas.saml-sp.rocket-chat.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.

cas.saml-sp.sa-manage.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.SAManage.

_{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:

cas.saml-sp.sa-manage.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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 -Dcas.saml-sp.sa-manage.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SA_MANAGE_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 --cas.saml-sp.sa-manage.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.

cas.saml-sp.safari-online.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.SafariOnline.

_{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:

cas.saml-sp.safari-online.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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 -Dcas.saml-sp.safari-online.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SAFARI_ONLINE_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 --cas.saml-sp.safari-online.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.

cas.saml-sp.salesforce.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Salesforce.

_{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:

cas.saml-sp.salesforce.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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 -Dcas.saml-sp.salesforce.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SALESFORCE_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 --cas.saml-sp.salesforce.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.

cas.saml-sp.sans-sth.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.SecuringTheHuman.

_{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:

cas.saml-sp.sans-sth.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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 -Dcas.saml-sp.sans-sth.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SANS_STH_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 --cas.saml-sp.sans-sth.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.

cas.saml-sp.service-now.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.ServiceNow.

_{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:

cas.saml-sp.service-now.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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 -Dcas.saml-sp.service-now.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SERVICE_NOW_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 --cas.saml-sp.service-now.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.

cas.saml-sp.slack.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Slack.

_{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:

cas.saml-sp.slack.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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 -Dcas.saml-sp.slack.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SLACK_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 --cas.saml-sp.slack.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.

cas.saml-sp.sserca.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.SunshineStateEdResearchAlliance.

_{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:

cas.saml-sp.sserca.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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 -Dcas.saml-sp.sserca.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SSERCA_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 --cas.saml-sp.sserca.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.

cas.saml-sp.symplicity.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Symplicity.

_{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:

cas.saml-sp.symplicity.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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 -Dcas.saml-sp.symplicity.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_SYMPLICITY_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 --cas.saml-sp.symplicity.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.

cas.saml-sp.tableau.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Tableau.

_{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:

cas.saml-sp.tableau.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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 -Dcas.saml-sp.tableau.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_TABLEAU_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 --cas.saml-sp.tableau.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.

cas.saml-sp.top-hat.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.TopHat.

_{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:

cas.saml-sp.top-hat.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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 -Dcas.saml-sp.top-hat.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_TOP_HAT_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 --cas.saml-sp.top-hat.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.

cas.saml-sp.warp-wire.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.WarpWire.

_{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:

cas.saml-sp.warp-wire.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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 -Dcas.saml-sp.warp-wire.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_WARP_WIRE_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 --cas.saml-sp.warp-wire.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.

cas.saml-sp.web-advisor.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.WebAdvisor.

_{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:

cas.saml-sp.web-advisor.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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 -Dcas.saml-sp.web-advisor.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_WEB_ADVISOR_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 --cas.saml-sp.web-advisor.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.

cas.saml-sp.webex.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Webex.

_{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:

cas.saml-sp.webex.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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 -Dcas.saml-sp.webex.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_WEBEX_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 --cas.saml-sp.webex.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.

cas.saml-sp.workday.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Workday.

_{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:

cas.saml-sp.workday.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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 -Dcas.saml-sp.workday.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_WORKDAY_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 --cas.saml-sp.workday.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.

cas.saml-sp.yuja.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Yuja.

_{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:

cas.saml-sp.yuja.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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 -Dcas.saml-sp.yuja.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_YUJA_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 --cas.saml-sp.yuja.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.

cas.saml-sp.zendesk.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Zendesk.

_{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:

cas.saml-sp.zendesk.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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 -Dcas.saml-sp.zendesk.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ZENDESK_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 --cas.saml-sp.zendesk.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.

cas.saml-sp.zimbra.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Zimbra.

_{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:

cas.saml-sp.zimbra.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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 -Dcas.saml-sp.zimbra.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ZIMBRA_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 --cas.saml-sp.zimbra.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.

cas.saml-sp.zoom.metadata=

The location of the metadata for this service provider. Can be a URL or another form of resource.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Zoom.

_{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:

cas.saml-sp.zoom.metadata=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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 -Dcas.saml-sp.zoom.metadata="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ZOOM_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 --cas.saml-sp.zoom.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.

# The location of the metadata for this service provider.
# cas.saml-sp.academic-health-plans.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.adobe-cloud.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.amazon.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.app-dynamics.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.arc-g-i-s.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.arms-software.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.asana.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.benefit-focus.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.black-baud.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.box.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.bynder.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.cccco.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.cher-well.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.concur-solutions.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.confluence.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.cranium-cafe.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.crash-plan.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.docu-sign.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.dropbox.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.easy-iep.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.egnyte.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.emma.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.ever-bridge.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.evernote.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.famis.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.gartner.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.gitlab.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.give-campus.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.in-common.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.infinite-campus.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.jira.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.neo-gov.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.net-partner.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.new-relic.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.office365.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.open-athens.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.pager-duty.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.poll-everywhere.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.qualtrics.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.rocket-chat.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.sa-manage.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.safari-online.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.salesforce.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.sans-sth.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.service-now.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.slack.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.sserca.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.symplicity.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.tableau.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.top-hat.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.warp-wire.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.web-advisor.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.webex.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.workday.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.yuja.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.zendesk.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.zimbra.metadata=

# The location of the metadata for this service provider.
# cas.saml-sp.zoom.metadata=

_{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.}

cas.saml-sp.academic-health-plans.attributes=

Set up the attribute release policy for this service. Allow attributes that are to be released to this SP. Attributes should be separated by commas and can be virtually mapped and renamed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      attributes: "..."

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 -Dcas.saml-sp.academic-health-plans.attributes="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_ATTRIBUTES="..."

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 --cas.saml-sp.academic-health-plans.attributes="..."

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.saml-sp.academic-health-plans.description= SAML SP Integration

Description of this service provider as it's stored in the registry.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      description: " SAML SP Integration"

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 -Dcas.saml-sp.academic-health-plans.description=" SAML SP Integration" -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_DESCRIPTION=" SAML SP Integration"

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 --cas.saml-sp.academic-health-plans.description=" SAML SP Integration"

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.saml-sp.academic-health-plans.entity-ids=

List of entityIds allowed for this service provider. Multiple ids can be specified in the event that the metadata is an aggregate.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      entity-ids: "..."

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 -Dcas.saml-sp.academic-health-plans.entity-ids="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_ENTITY_IDS="..."

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 --cas.saml-sp.academic-health-plans.entity-ids="..."

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.saml-sp.academic-health-plans.name=

Name of this service provider.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      name: "..."

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 -Dcas.saml-sp.academic-health-plans.name="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_NAME="..."

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 --cas.saml-sp.academic-health-plans.name="..."

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.saml-sp.academic-health-plans.name-id-attribute=

Attribute to use when generating nameids for this SP.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.name-id-attribute=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      name-id-attribute: "..."

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 -Dcas.saml-sp.academic-health-plans.name-id-attribute="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_NAME_ID_ATTRIBUTE="..."

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 --cas.saml-sp.academic-health-plans.name-id-attribute="..."

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.saml-sp.academic-health-plans.name-id-format=

The forced nameId format to use when generating a response.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.name-id-format=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      name-id-format: "..."

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 -Dcas.saml-sp.academic-health-plans.name-id-format="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_NAME_ID_FORMAT="..."

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 --cas.saml-sp.academic-health-plans.name-id-format="..."

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.saml-sp.academic-health-plans.sign-assertions=

Indicate whether assertions should be signed. Available values are as follows:

TRUE: Constant to represent the true state.
FALSE: Constant to represent the false state.
UNDEFINED: Constant to represent the undefined state.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      sign-assertions: "..."

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 -Dcas.saml-sp.academic-health-plans.sign-assertions="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_SIGN_ASSERTIONS="..."

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 --cas.saml-sp.academic-health-plans.sign-assertions="..."

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.saml-sp.academic-health-plans.sign-responses=true

Indicate whether responses should be signed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.sign-responses=true

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      sign-responses: "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 -Dcas.saml-sp.academic-health-plans.sign-responses="true" -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_SIGN_RESPONSES="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 --cas.saml-sp.academic-health-plans.sign-responses="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.

cas.saml-sp.academic-health-plans.signature-location=

Signature location used to verify metadata.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AcademicHealthPlans.

_{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:

cas.saml-sp.academic-health-plans.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    academic-health-plans: 
      signature-location: "..."

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 -Dcas.saml-sp.academic-health-plans.signature-location="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ACADEMIC_HEALTH_PLANS_SIGNATURE_LOCATION="..."

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 --cas.saml-sp.academic-health-plans.signature-location="..."

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.saml-sp.adobe-cloud.attributes=

Set up the attribute release policy for this service. Allow attributes that are to be released to this SP. Attributes should be separated by commas and can be virtually mapped and renamed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      attributes: "..."

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 -Dcas.saml-sp.adobe-cloud.attributes="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_ATTRIBUTES="..."

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 --cas.saml-sp.adobe-cloud.attributes="..."

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.saml-sp.adobe-cloud.description= SAML SP Integration

Description of this service provider as it's stored in the registry.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      description: " SAML SP Integration"

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 -Dcas.saml-sp.adobe-cloud.description=" SAML SP Integration" -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_DESCRIPTION=" SAML SP Integration"

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 --cas.saml-sp.adobe-cloud.description=" SAML SP Integration"

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.saml-sp.adobe-cloud.entity-ids=

List of entityIds allowed for this service provider. Multiple ids can be specified in the event that the metadata is an aggregate.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      entity-ids: "..."

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 -Dcas.saml-sp.adobe-cloud.entity-ids="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_ENTITY_IDS="..."

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 --cas.saml-sp.adobe-cloud.entity-ids="..."

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.saml-sp.adobe-cloud.name=

Name of this service provider.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      name: "..."

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 -Dcas.saml-sp.adobe-cloud.name="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_NAME="..."

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 --cas.saml-sp.adobe-cloud.name="..."

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.saml-sp.adobe-cloud.name-id-attribute=

Attribute to use when generating nameids for this SP.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.name-id-attribute=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      name-id-attribute: "..."

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 -Dcas.saml-sp.adobe-cloud.name-id-attribute="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_NAME_ID_ATTRIBUTE="..."

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 --cas.saml-sp.adobe-cloud.name-id-attribute="..."

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.saml-sp.adobe-cloud.name-id-format=

The forced nameId format to use when generating a response.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.name-id-format=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      name-id-format: "..."

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 -Dcas.saml-sp.adobe-cloud.name-id-format="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_NAME_ID_FORMAT="..."

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 --cas.saml-sp.adobe-cloud.name-id-format="..."

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.saml-sp.adobe-cloud.sign-assertions=

Indicate whether assertions should be signed. Available values are as follows:

TRUE: Constant to represent the true state.
FALSE: Constant to represent the false state.
UNDEFINED: Constant to represent the undefined state.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      sign-assertions: "..."

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 -Dcas.saml-sp.adobe-cloud.sign-assertions="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_SIGN_ASSERTIONS="..."

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 --cas.saml-sp.adobe-cloud.sign-assertions="..."

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.saml-sp.adobe-cloud.sign-responses=true

Indicate whether responses should be signed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.sign-responses=true

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      sign-responses: "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 -Dcas.saml-sp.adobe-cloud.sign-responses="true" -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_SIGN_RESPONSES="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 --cas.saml-sp.adobe-cloud.sign-responses="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.

cas.saml-sp.adobe-cloud.signature-location=

Signature location used to verify metadata.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AdobeCloud.

_{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:

cas.saml-sp.adobe-cloud.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    adobe-cloud: 
      signature-location: "..."

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 -Dcas.saml-sp.adobe-cloud.signature-location="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_ADOBE_CLOUD_SIGNATURE_LOCATION="..."

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 --cas.saml-sp.adobe-cloud.signature-location="..."

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.saml-sp.amazon.attributes=

Set up the attribute release policy for this service. Allow attributes that are to be released to this SP. Attributes should be separated by commas and can be virtually mapped and renamed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      attributes: "..."

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 -Dcas.saml-sp.amazon.attributes="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_ATTRIBUTES="..."

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 --cas.saml-sp.amazon.attributes="..."

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.saml-sp.amazon.description= SAML SP Integration

Description of this service provider as it's stored in the registry.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      description: " SAML SP Integration"

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 -Dcas.saml-sp.amazon.description=" SAML SP Integration" -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_DESCRIPTION=" SAML SP Integration"

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 --cas.saml-sp.amazon.description=" SAML SP Integration"

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.saml-sp.amazon.entity-ids=

List of entityIds allowed for this service provider. Multiple ids can be specified in the event that the metadata is an aggregate.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      entity-ids: "..."

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 -Dcas.saml-sp.amazon.entity-ids="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_ENTITY_IDS="..."

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 --cas.saml-sp.amazon.entity-ids="..."

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.saml-sp.amazon.name=

Name of this service provider.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      name: "..."

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 -Dcas.saml-sp.amazon.name="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_NAME="..."

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 --cas.saml-sp.amazon.name="..."

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.saml-sp.amazon.name-id-attribute=

Attribute to use when generating nameids for this SP.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.name-id-attribute=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      name-id-attribute: "..."

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 -Dcas.saml-sp.amazon.name-id-attribute="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_NAME_ID_ATTRIBUTE="..."

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 --cas.saml-sp.amazon.name-id-attribute="..."

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.saml-sp.amazon.name-id-format=

The forced nameId format to use when generating a response.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.name-id-format=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      name-id-format: "..."

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 -Dcas.saml-sp.amazon.name-id-format="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_NAME_ID_FORMAT="..."

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 --cas.saml-sp.amazon.name-id-format="..."

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.saml-sp.amazon.sign-assertions=

Indicate whether assertions should be signed. Available values are as follows:

TRUE: Constant to represent the true state.
FALSE: Constant to represent the false state.
UNDEFINED: Constant to represent the undefined state.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      sign-assertions: "..."

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 -Dcas.saml-sp.amazon.sign-assertions="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_SIGN_ASSERTIONS="..."

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 --cas.saml-sp.amazon.sign-assertions="..."

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.saml-sp.amazon.sign-responses=true

Indicate whether responses should be signed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.sign-responses=true

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      sign-responses: "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 -Dcas.saml-sp.amazon.sign-responses="true" -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_SIGN_RESPONSES="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 --cas.saml-sp.amazon.sign-responses="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.

cas.saml-sp.amazon.signature-location=

Signature location used to verify metadata.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.Amazon.

_{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:

cas.saml-sp.amazon.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    amazon: 
      signature-location: "..."

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 -Dcas.saml-sp.amazon.signature-location="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_AMAZON_SIGNATURE_LOCATION="..."

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 --cas.saml-sp.amazon.signature-location="..."

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.saml-sp.app-dynamics.attributes=

Set up the attribute release policy for this service. Allow attributes that are to be released to this SP. Attributes should be separated by commas and can be virtually mapped and renamed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      attributes: "..."

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 -Dcas.saml-sp.app-dynamics.attributes="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_ATTRIBUTES="..."

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 --cas.saml-sp.app-dynamics.attributes="..."

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.saml-sp.app-dynamics.description= SAML SP Integration

Description of this service provider as it's stored in the registry.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      description: " SAML SP Integration"

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 -Dcas.saml-sp.app-dynamics.description=" SAML SP Integration" -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_DESCRIPTION=" SAML SP Integration"

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 --cas.saml-sp.app-dynamics.description=" SAML SP Integration"

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.saml-sp.app-dynamics.entity-ids=

List of entityIds allowed for this service provider. Multiple ids can be specified in the event that the metadata is an aggregate.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      entity-ids: "..."

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 -Dcas.saml-sp.app-dynamics.entity-ids="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_ENTITY_IDS="..."

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 --cas.saml-sp.app-dynamics.entity-ids="..."

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.saml-sp.app-dynamics.name=

Name of this service provider.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      name: "..."

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 -Dcas.saml-sp.app-dynamics.name="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_NAME="..."

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 --cas.saml-sp.app-dynamics.name="..."

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.saml-sp.app-dynamics.name-id-attribute=

Attribute to use when generating nameids for this SP.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.name-id-attribute=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      name-id-attribute: "..."

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 -Dcas.saml-sp.app-dynamics.name-id-attribute="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_NAME_ID_ATTRIBUTE="..."

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 --cas.saml-sp.app-dynamics.name-id-attribute="..."

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.saml-sp.app-dynamics.name-id-format=

The forced nameId format to use when generating a response.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.name-id-format=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      name-id-format: "..."

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 -Dcas.saml-sp.app-dynamics.name-id-format="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_NAME_ID_FORMAT="..."

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 --cas.saml-sp.app-dynamics.name-id-format="..."

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.saml-sp.app-dynamics.sign-assertions=

Indicate whether assertions should be signed. Available values are as follows:

TRUE: Constant to represent the true state.
FALSE: Constant to represent the false state.
UNDEFINED: Constant to represent the undefined state.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      sign-assertions: "..."

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 -Dcas.saml-sp.app-dynamics.sign-assertions="..." -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_SIGN_ASSERTIONS="..."

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 --cas.saml-sp.app-dynamics.sign-assertions="..."

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.saml-sp.app-dynamics.sign-responses=true

Indicate whether responses should be signed.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{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:

cas.saml-sp.app-dynamics.sign-responses=true

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      sign-responses: "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 -Dcas.saml-sp.app-dynamics.sign-responses="true" -jar build/libs/cas.war

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

export CAS_SAML_SP_APP_DYNAMICS_SIGN_RESPONSES="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 --cas.saml-sp.app-dynamics.sign-responses="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.

cas.saml-sp.app-dynamics.signature-location=

Signature location used to verify metadata.

org.apereo.cas.configuration.model.support.saml.sps.SamlServiceProviderProperties.AppDynamics.

_{How can I configure this property?}