WORKERS AHEAD!

You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. You are most encouraged to test the changes presented.

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

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    app-dynamics: 
      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.app-dynamics.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_APP_DYNAMICS_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.app-dynamics.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.arc-g-i-s.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arc-g-i-s.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arc-g-i-s: 
      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.arc-g-i-s.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_ARC_G_I_S_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.arc-g-i-s.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.arms-software.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.arms-software.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    arms-software: 
      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.arms-software.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_ARMS_SOFTWARE_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.arms-software.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.asana.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.asana.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    asana: 
      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.asana.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_ASANA_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.asana.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.benefit-focus.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.benefit-focus.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    benefit-focus: 
      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.benefit-focus.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_BENEFIT_FOCUS_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.benefit-focus.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.black-baud.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.black-baud.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    black-baud: 
      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.black-baud.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_BLACK_BAUD_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.black-baud.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.box.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.box.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    box: 
      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.box.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_BOX_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.box.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.bynder.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.bynder.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    bynder: 
      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.bynder.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_BYNDER_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.bynder.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.cccco.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cccco.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cccco: 
      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.cccco.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_CCCCO_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.cccco.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.cher-well.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.cher-well.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cher-well: 
      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.cher-well.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_CHER_WELL_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.cher-well.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.concur-solutions.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.concur-solutions.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    concur-solutions: 
      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.concur-solutions.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_CONCUR_SOLUTIONS_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.concur-solutions.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.confluence.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.confluence.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    confluence: 
      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.confluence.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_CONFLUENCE_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.confluence.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.cranium-cafe.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.cranium-cafe.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    cranium-cafe: 
      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.cranium-cafe.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_CRANIUM_CAFE_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.cranium-cafe.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.crash-plan.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.crash-plan.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    crash-plan: 
      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.crash-plan.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_CRASH_PLAN_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.crash-plan.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.docu-sign.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.docu-sign.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    docu-sign: 
      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.docu-sign.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_DOCU_SIGN_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.docu-sign.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.dropbox.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.dropbox.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    dropbox: 
      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.dropbox.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_DROPBOX_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.dropbox.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.easy-iep.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.easy-iep.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    easy-iep: 
      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.easy-iep.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_EASY_IEP_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.easy-iep.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.egnyte.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.egnyte.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    egnyte: 
      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.egnyte.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_EGNYTE_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.egnyte.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.emma.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.emma.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    emma: 
      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.emma.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_EMMA_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.emma.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.ever-bridge.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.ever-bridge.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    ever-bridge: 
      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.ever-bridge.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_EVER_BRIDGE_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.ever-bridge.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.evernote.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.evernote.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    evernote: 
      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.evernote.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_EVERNOTE_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.evernote.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.famis.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.famis.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    famis: 
      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.famis.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_FAMIS_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.famis.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.gartner.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gartner.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gartner: 
      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.gartner.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_GARTNER_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.gartner.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.gitlab.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.gitlab.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    gitlab: 
      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.gitlab.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_GITLAB_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.gitlab.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.give-campus.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.give-campus.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    give-campus: 
      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.give-campus.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_GIVE_CAMPUS_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.give-campus.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.in-common.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.in-common.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    in-common: 
      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.in-common.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_IN_COMMON_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.in-common.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.infinite-campus.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.infinite-campus.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    infinite-campus: 
      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.infinite-campus.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_INFINITE_CAMPUS_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.infinite-campus.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.jira.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.jira.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    jira: 
      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.jira.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_JIRA_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.jira.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.neo-gov.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.neo-gov.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    neo-gov: 
      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.neo-gov.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_NEO_GOV_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.neo-gov.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.net-partner.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.net-partner.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    net-partner: 
      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.net-partner.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_NET_PARTNER_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.net-partner.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.new-relic.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.new-relic.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    new-relic: 
      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.new-relic.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_NEW_RELIC_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.new-relic.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.office365.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.office365.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    office365: 
      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.office365.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_OFFICE365_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.office365.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.open-athens.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.open-athens.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    open-athens: 
      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.open-athens.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_OPEN_ATHENS_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.open-athens.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.pager-duty.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.pager-duty.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    pager-duty: 
      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.pager-duty.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_PAGER_DUTY_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.pager-duty.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.poll-everywhere.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.poll-everywhere.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    poll-everywhere: 
      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.poll-everywhere.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_POLL_EVERYWHERE_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.poll-everywhere.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.qualtrics.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.qualtrics.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    qualtrics: 
      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.qualtrics.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_QUALTRICS_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.qualtrics.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.rocket-chat.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.rocket-chat.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    rocket-chat: 
      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.rocket-chat.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_ROCKET_CHAT_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.rocket-chat.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.sa-manage.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.sa-manage.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sa-manage: 
      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.sa-manage.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_SA_MANAGE_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.sa-manage.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.safari-online.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.safari-online.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    safari-online: 
      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.safari-online.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_SAFARI_ONLINE_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.safari-online.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.salesforce.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.salesforce.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    salesforce: 
      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.salesforce.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_SALESFORCE_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.salesforce.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.sans-sth.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.sans-sth.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sans-sth: 
      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.sans-sth.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_SANS_STH_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.sans-sth.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.service-now.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.service-now.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    service-now: 
      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.service-now.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_SERVICE_NOW_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.service-now.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.slack.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.slack.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    slack: 
      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.slack.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_SLACK_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.slack.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.sserca.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.sserca.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    sserca: 
      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.sserca.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_SSERCA_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.sserca.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.symplicity.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.symplicity.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    symplicity: 
      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.symplicity.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_SYMPLICITY_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.symplicity.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.tableau.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.tableau.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    tableau: 
      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.tableau.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_TABLEAU_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.tableau.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.top-hat.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.top-hat.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    top-hat: 
      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.top-hat.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_TOP_HAT_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.top-hat.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.warp-wire.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.warp-wire.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    warp-wire: 
      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.warp-wire.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_WARP_WIRE_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.warp-wire.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.web-advisor.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.web-advisor.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    web-advisor: 
      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.web-advisor.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_WEB_ADVISOR_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.web-advisor.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.webex.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.webex.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    webex: 
      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.webex.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_WEBEX_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.webex.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.workday.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.workday.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    workday: 
      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.workday.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_WORKDAY_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.workday.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.yuja.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.yuja.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    yuja: 
      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.yuja.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_YUJA_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.yuja.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.zendesk.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zendesk.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zendesk: 
      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.zendesk.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_ZENDESK_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.zendesk.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.zimbra.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zimbra.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zimbra: 
      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.zimbra.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_ZIMBRA_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.zimbra.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.zoom.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.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.attributes=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.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.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.description= SAML SP Integration

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.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.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.entity-ids=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.name=

Name of this service provider.

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.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.name-id-attribute=

Attribute to use when generating nameids for this SP.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.name-id-format=

The forced nameId format to use when generating a response.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.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.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.sign-assertions=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.sign-responses=true

Indicate whether responses should be signed.

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

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.zoom.signature-location=

Signature location used to verify metadata.

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.signature-location=...

CAS properties can be specified using the YAML syntax:

cas: 
  saml-sp: 
    zoom: 
      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.zoom.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_ZOOM_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.zoom.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.

# Set up the attribute release policy for this service.
# cas.saml-sp.academic-health-plans.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.academic-health-plans.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.academic-health-plans.entity-ids=

# Name of this service provider.
# cas.saml-sp.academic-health-plans.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.academic-health-plans.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.academic-health-plans.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.academic-health-plans.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.academic-health-plans.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.academic-health-plans.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.adobe-cloud.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.adobe-cloud.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.adobe-cloud.entity-ids=

# Name of this service provider.
# cas.saml-sp.adobe-cloud.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.adobe-cloud.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.adobe-cloud.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.adobe-cloud.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.adobe-cloud.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.adobe-cloud.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.amazon.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.amazon.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.amazon.entity-ids=

# Name of this service provider.
# cas.saml-sp.amazon.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.amazon.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.amazon.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.amazon.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.amazon.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.amazon.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.app-dynamics.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.app-dynamics.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.app-dynamics.entity-ids=

# Name of this service provider.
# cas.saml-sp.app-dynamics.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.app-dynamics.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.app-dynamics.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.app-dynamics.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.app-dynamics.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.app-dynamics.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.arc-g-i-s.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.arc-g-i-s.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.arc-g-i-s.entity-ids=

# Name of this service provider.
# cas.saml-sp.arc-g-i-s.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.arc-g-i-s.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.arc-g-i-s.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.arc-g-i-s.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.arc-g-i-s.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.arc-g-i-s.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.arms-software.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.arms-software.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.arms-software.entity-ids=

# Name of this service provider.
# cas.saml-sp.arms-software.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.arms-software.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.arms-software.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.arms-software.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.arms-software.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.arms-software.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.asana.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.asana.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.asana.entity-ids=

# Name of this service provider.
# cas.saml-sp.asana.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.asana.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.asana.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.asana.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.asana.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.asana.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.benefit-focus.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.benefit-focus.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.benefit-focus.entity-ids=

# Name of this service provider.
# cas.saml-sp.benefit-focus.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.benefit-focus.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.benefit-focus.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.benefit-focus.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.benefit-focus.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.benefit-focus.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.black-baud.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.black-baud.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.black-baud.entity-ids=

# Name of this service provider.
# cas.saml-sp.black-baud.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.black-baud.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.black-baud.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.black-baud.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.black-baud.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.black-baud.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.box.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.box.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.box.entity-ids=

# Name of this service provider.
# cas.saml-sp.box.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.box.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.box.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.box.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.box.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.box.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.bynder.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.bynder.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.bynder.entity-ids=

# Name of this service provider.
# cas.saml-sp.bynder.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.bynder.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.bynder.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.bynder.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.bynder.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.bynder.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.cccco.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.cccco.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.cccco.entity-ids=

# Name of this service provider.
# cas.saml-sp.cccco.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.cccco.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.cccco.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.cccco.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.cccco.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.cccco.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.cher-well.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.cher-well.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.cher-well.entity-ids=

# Name of this service provider.
# cas.saml-sp.cher-well.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.cher-well.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.cher-well.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.cher-well.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.cher-well.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.cher-well.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.concur-solutions.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.concur-solutions.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.concur-solutions.entity-ids=

# Name of this service provider.
# cas.saml-sp.concur-solutions.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.concur-solutions.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.concur-solutions.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.concur-solutions.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.concur-solutions.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.concur-solutions.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.confluence.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.confluence.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.confluence.entity-ids=

# Name of this service provider.
# cas.saml-sp.confluence.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.confluence.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.confluence.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.confluence.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.confluence.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.confluence.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.cranium-cafe.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.cranium-cafe.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.cranium-cafe.entity-ids=

# Name of this service provider.
# cas.saml-sp.cranium-cafe.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.cranium-cafe.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.cranium-cafe.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.cranium-cafe.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.cranium-cafe.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.cranium-cafe.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.crash-plan.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.crash-plan.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.crash-plan.entity-ids=

# Name of this service provider.
# cas.saml-sp.crash-plan.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.crash-plan.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.crash-plan.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.crash-plan.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.crash-plan.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.crash-plan.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.docu-sign.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.docu-sign.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.docu-sign.entity-ids=

# Name of this service provider.
# cas.saml-sp.docu-sign.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.docu-sign.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.docu-sign.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.docu-sign.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.docu-sign.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.docu-sign.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.dropbox.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.dropbox.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.dropbox.entity-ids=

# Name of this service provider.
# cas.saml-sp.dropbox.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.dropbox.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.dropbox.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.dropbox.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.dropbox.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.dropbox.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.easy-iep.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.easy-iep.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.easy-iep.entity-ids=

# Name of this service provider.
# cas.saml-sp.easy-iep.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.easy-iep.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.easy-iep.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.easy-iep.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.easy-iep.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.easy-iep.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.egnyte.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.egnyte.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.egnyte.entity-ids=

# Name of this service provider.
# cas.saml-sp.egnyte.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.egnyte.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.egnyte.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.egnyte.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.egnyte.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.egnyte.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.emma.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.emma.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.emma.entity-ids=

# Name of this service provider.
# cas.saml-sp.emma.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.emma.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.emma.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.emma.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.emma.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.emma.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.ever-bridge.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.ever-bridge.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.ever-bridge.entity-ids=

# Name of this service provider.
# cas.saml-sp.ever-bridge.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.ever-bridge.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.ever-bridge.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.ever-bridge.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.ever-bridge.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.ever-bridge.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.evernote.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.evernote.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.evernote.entity-ids=

# Name of this service provider.
# cas.saml-sp.evernote.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.evernote.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.evernote.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.evernote.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.evernote.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.evernote.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.famis.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.famis.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.famis.entity-ids=

# Name of this service provider.
# cas.saml-sp.famis.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.famis.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.famis.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.famis.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.famis.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.famis.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.gartner.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.gartner.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.gartner.entity-ids=

# Name of this service provider.
# cas.saml-sp.gartner.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.gartner.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.gartner.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.gartner.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.gartner.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.gartner.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.gitlab.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.gitlab.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.gitlab.entity-ids=

# Name of this service provider.
# cas.saml-sp.gitlab.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.gitlab.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.gitlab.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.gitlab.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.gitlab.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.gitlab.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.give-campus.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.give-campus.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.give-campus.entity-ids=

# Name of this service provider.
# cas.saml-sp.give-campus.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.give-campus.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.give-campus.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.give-campus.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.give-campus.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.give-campus.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.in-common.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.in-common.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.in-common.entity-ids=

# Name of this service provider.
# cas.saml-sp.in-common.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.in-common.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.in-common.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.in-common.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.in-common.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.in-common.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.infinite-campus.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.infinite-campus.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.infinite-campus.entity-ids=

# Name of this service provider.
# cas.saml-sp.infinite-campus.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.infinite-campus.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.infinite-campus.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.infinite-campus.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.infinite-campus.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.infinite-campus.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.jira.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.jira.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.jira.entity-ids=

# Name of this service provider.
# cas.saml-sp.jira.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.jira.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.jira.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.jira.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.jira.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.jira.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.neo-gov.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.neo-gov.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.neo-gov.entity-ids=

# Name of this service provider.
# cas.saml-sp.neo-gov.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.neo-gov.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.neo-gov.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.neo-gov.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.neo-gov.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.neo-gov.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.net-partner.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.net-partner.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.net-partner.entity-ids=

# Name of this service provider.
# cas.saml-sp.net-partner.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.net-partner.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.net-partner.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.net-partner.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.net-partner.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.net-partner.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.new-relic.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.new-relic.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.new-relic.entity-ids=

# Name of this service provider.
# cas.saml-sp.new-relic.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.new-relic.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.new-relic.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.new-relic.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.new-relic.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.new-relic.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.office365.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.office365.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.office365.entity-ids=

# Name of this service provider.
# cas.saml-sp.office365.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.office365.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.office365.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.office365.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.office365.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.office365.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.open-athens.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.open-athens.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.open-athens.entity-ids=

# Name of this service provider.
# cas.saml-sp.open-athens.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.open-athens.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.open-athens.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.open-athens.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.open-athens.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.open-athens.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.pager-duty.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.pager-duty.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.pager-duty.entity-ids=

# Name of this service provider.
# cas.saml-sp.pager-duty.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.pager-duty.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.pager-duty.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.pager-duty.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.pager-duty.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.pager-duty.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.poll-everywhere.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.poll-everywhere.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.poll-everywhere.entity-ids=

# Name of this service provider.
# cas.saml-sp.poll-everywhere.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.poll-everywhere.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.poll-everywhere.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.poll-everywhere.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.poll-everywhere.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.poll-everywhere.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.qualtrics.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.qualtrics.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.qualtrics.entity-ids=

# Name of this service provider.
# cas.saml-sp.qualtrics.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.qualtrics.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.qualtrics.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.qualtrics.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.qualtrics.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.qualtrics.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.rocket-chat.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.rocket-chat.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.rocket-chat.entity-ids=

# Name of this service provider.
# cas.saml-sp.rocket-chat.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.rocket-chat.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.rocket-chat.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.rocket-chat.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.rocket-chat.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.rocket-chat.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.sa-manage.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.sa-manage.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.sa-manage.entity-ids=

# Name of this service provider.
# cas.saml-sp.sa-manage.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.sa-manage.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.sa-manage.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.sa-manage.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.sa-manage.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.sa-manage.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.safari-online.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.safari-online.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.safari-online.entity-ids=

# Name of this service provider.
# cas.saml-sp.safari-online.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.safari-online.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.safari-online.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.safari-online.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.safari-online.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.safari-online.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.salesforce.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.salesforce.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.salesforce.entity-ids=

# Name of this service provider.
# cas.saml-sp.salesforce.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.salesforce.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.salesforce.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.salesforce.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.salesforce.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.salesforce.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.sans-sth.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.sans-sth.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.sans-sth.entity-ids=

# Name of this service provider.
# cas.saml-sp.sans-sth.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.sans-sth.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.sans-sth.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.sans-sth.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.sans-sth.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.sans-sth.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.service-now.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.service-now.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.service-now.entity-ids=

# Name of this service provider.
# cas.saml-sp.service-now.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.service-now.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.service-now.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.service-now.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.service-now.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.service-now.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.slack.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.slack.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.slack.entity-ids=

# Name of this service provider.
# cas.saml-sp.slack.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.slack.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.slack.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.slack.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.slack.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.slack.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.sserca.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.sserca.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.sserca.entity-ids=

# Name of this service provider.
# cas.saml-sp.sserca.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.sserca.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.sserca.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.sserca.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.sserca.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.sserca.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.symplicity.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.symplicity.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.symplicity.entity-ids=

# Name of this service provider.
# cas.saml-sp.symplicity.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.symplicity.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.symplicity.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.symplicity.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.symplicity.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.symplicity.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.tableau.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.tableau.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.tableau.entity-ids=

# Name of this service provider.
# cas.saml-sp.tableau.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.tableau.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.tableau.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.tableau.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.tableau.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.tableau.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.top-hat.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.top-hat.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.top-hat.entity-ids=

# Name of this service provider.
# cas.saml-sp.top-hat.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.top-hat.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.top-hat.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.top-hat.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.top-hat.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.top-hat.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.warp-wire.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.warp-wire.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.warp-wire.entity-ids=

# Name of this service provider.
# cas.saml-sp.warp-wire.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.warp-wire.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.warp-wire.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.warp-wire.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.warp-wire.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.warp-wire.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.web-advisor.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.web-advisor.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.web-advisor.entity-ids=

# Name of this service provider.
# cas.saml-sp.web-advisor.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.web-advisor.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.web-advisor.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.web-advisor.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.web-advisor.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.web-advisor.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.webex.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.webex.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.webex.entity-ids=

# Name of this service provider.
# cas.saml-sp.webex.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.webex.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.webex.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.webex.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.webex.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.webex.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.workday.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.workday.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.workday.entity-ids=

# Name of this service provider.
# cas.saml-sp.workday.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.workday.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.workday.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.workday.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.workday.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.workday.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.yuja.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.yuja.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.yuja.entity-ids=

# Name of this service provider.
# cas.saml-sp.yuja.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.yuja.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.yuja.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.yuja.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.yuja.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.yuja.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.zendesk.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.zendesk.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.zendesk.entity-ids=

# Name of this service provider.
# cas.saml-sp.zendesk.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.zendesk.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.zendesk.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.zendesk.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.zendesk.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.zendesk.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.zimbra.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.zimbra.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.zimbra.entity-ids=

# Name of this service provider.
# cas.saml-sp.zimbra.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.zimbra.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.zimbra.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.zimbra.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.zimbra.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.zimbra.signature-location=

# Set up the attribute release policy for this service.
# cas.saml-sp.zoom.attributes=

# Description of this service provider as it's stored in the registry.
# cas.saml-sp.zoom.description= SAML SP Integration

# List of entityIds allowed for this service provider.
# cas.saml-sp.zoom.entity-ids=

# Name of this service provider.
# cas.saml-sp.zoom.name=

# Attribute to use when generating nameids for this SP.
# cas.saml-sp.zoom.name-id-attribute=

# The forced nameId format to use when generating a response.
# cas.saml-sp.zoom.name-id-format=

# Indicate whether assertions should be signed.
# cas.saml-sp.zoom.sign-assertions=

# Indicate whether responses should be signed.
# cas.saml-sp.zoom.sign-responses=true

# Signature location used to verify metadata.
# cas.saml-sp.zoom.signature-location=

Configuration Metadata

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

Be Selective

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

YAGNI

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

Naming Convention

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

Note

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

Validation

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

Indexed Settings

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

Note: For InCommon and other metadata aggregates, multiple entity ids can be specified to filter the InCommon metadata. EntityIds can be regular expression patterns and are mapped to CAS’ serviceId field in the registry. The signature location MUST BE the public key used to sign the metadata.