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.

OpenID Connect Generic

For an overview of the delegated authentication flow, please see this guide.

Support is enabled by including the following dependency in the WAR overlay:

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

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

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

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

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-pac4j-oidc"
}

Configuration

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.authn.pac4j.oidc[0].generic.discovery-uri=

The discovery endpoint to locate the provider metadata.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{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.authn.pac4j.oidc[0].generic.discovery-uri=...

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: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          discovery-uri: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.discovery-uri="..." -jar build/libs/cas.war

The above example assumes 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_AUTHN_PAC4J_OIDC[0]_GENERIC_DISCOVERY_URI="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.discovery-uri="..."

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

cas.authn.pac4j.oidc[0].generic.id=

The client id.

This setting supports the Spring Expression Language.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.id=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          id: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.id="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.id="..."

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

cas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.location=

Specific JWKS for the private_key_jwt client authentication method. The location of the resource. Resources can be URLs, or files found either on the classpath or outside somewhere in the file system.

In the event the configured resource is a Groovy script, especially if the script is set to reload on changes, you may need to adjust the total number of inotify instances. On Linux, you may need to add the following line to /etc/sysctl.conf: fs.inotify.max_user_instances = 256.

You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.

In situations and scenarios where CAS is able to automatically watch the underlying resource for changes and detect updates and modifications dynamically, you may be able to specify the following setting as either an environment variable or system property with a value of false to disable the resource watcher: org.apereo.cas.util.io.PathWatcherService.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.location=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          private-key-jwt: 
            jwks: 
              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.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.location="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_PRIVATE_KEY_JWT_JWKS_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.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.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.authn.pac4j.oidc[0].generic.secret=

The client secret.

This setting supports the Spring Expression Language.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.secret=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          secret: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.secret="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_SECRET="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.secret="..."

The above example assumes 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 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.authn.pac4j.oidc[0].generic.allow-unsigned-id-tokens=

Whether unsigned id tokens issued as plain JWTs are accepted.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.allow-unsigned-id-tokens=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          allow-unsigned-id-tokens: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.allow-unsigned-id-tokens="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_ALLOW_UNSIGNED_ID_TOKENS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.allow-unsigned-id-tokens="..."

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

cas.authn.pac4j.oidc[0].generic.auto-redirect-type=NONE

Auto-redirect to this client. Available values are as follows:

SERVER: Redirect on the server side, typically making CAS invisible.
CLIENT: Redirect on the client side using browser redirects, etc.
NONE: Do nothing and let the selection take place manually.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.auto-redirect-type=NONE

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          auto-redirect-type: "NONE"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.auto-redirect-type="NONE" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_AUTO_REDIRECT_TYPE="NONE"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.auto-redirect-type="NONE"

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

cas.authn.pac4j.oidc[0].generic.callback-url=

Callback URL to use to return the flow back to the CAS server one the identity provider is successfully done. This may be used at the discretion of the client and its type to build service parameters, redirect URIs, etc. If none is specified, the CAS server's login endpoint will be used as the basis of the final callback url.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.callback-url=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          callback-url: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.callback-url="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CALLBACK_URL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.callback-url="..."

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

cas.authn.pac4j.oidc[0].generic.callback-url-type=QUERY_PARAMETER

Determine how the callback url should be resolved. Default is CallbackUrlTypes#QUERY_PARAMETER. Available values are as follows:

PATH_PARAMETER: Path parameter callback url. The client name is added to the path of the callback URL.
QUERY_PARAMETER: Query parameter callback url. The client name is added to the path of a query parameter.
NONE: No callback url. No name is added to the callback URL to be able to distinguish the client.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.callback-url-type=QUERY_PARAMETER

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          callback-url-type: "QUERY_PARAMETER"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.callback-url-type="QUERY_PARAMETER" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CALLBACK_URL_TYPE="QUERY_PARAMETER"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.callback-url-type="QUERY_PARAMETER"

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

cas.authn.pac4j.oidc[0].generic.client-authentication-method=

The preferred client authentication method that will be chosen for token requests. If none is specified, one will be chosen somewhat randomly based on what the OIDC OP supports.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.client-authentication-method=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          client-authentication-method: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.client-authentication-method="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CLIENT_AUTHENTICATION_METHOD="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.client-authentication-method="..."

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

cas.authn.pac4j.oidc[0].generic.client-name=

Name of the client mostly for UI purposes and uniqueness. This name, with 'non-word' characters converted to '-' (e.g. "This Org (New)" becomes "This-Org--New-") is added to the "class" attribute of the redirect link on the login page, to allow for custom styling of individual IdPs (e.g. for an organization logo).

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.client-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          client-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.authn.pac4j.oidc[0].generic.client-name="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CLIENT_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.authn.pac4j.oidc[0].generic.client-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.authn.pac4j.oidc[0].generic.connect-timeout=

Read timeout of the OIDC client.

This settings supports the java.time.Duration syntax ^[?].

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.connect-timeout=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          connect-timeout: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.connect-timeout="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.connect-timeout="..."

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

cas.authn.pac4j.oidc[0].generic.css-class=

CSS class that should be assigned to this client.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.css-class=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          css-class: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.css-class="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CSS_CLASS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.css-class="..."

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

cas.authn.pac4j.oidc[0].generic.custom-params=

Custom parameters to send along in authZ requests, etc.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.custom-params=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          custom-params: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.custom-params="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_CUSTOM_PARAMS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.custom-params="..."

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

cas.authn.pac4j.oidc[0].generic.disable-pkce=

Disable PKCE support for the provider.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.disable-pkce=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          disable-pkce: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.disable-pkce="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_DISABLE_PKCE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.disable-pkce="..."

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

cas.authn.pac4j.oidc[0].generic.display-name=

Indicate the title or display name of the client for decoration and client presentation purposes. If left blank, the client original name would be used by default.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.display-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          display-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.authn.pac4j.oidc[0].generic.display-name="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_DISPLAY_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.authn.pac4j.oidc[0].generic.display-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.authn.pac4j.oidc[0].generic.enabled=true

Whether the client/external identity provider should be considered active and enabled for integration purposes.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.enabled=true

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          enabled: "true"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.enabled="true" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_ENABLED="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.enabled="true"

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

cas.authn.pac4j.oidc[0].generic.expire-session-with-token=

Checks if sessions expire with token expiration.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.expire-session-with-token=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          expire-session-with-token: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.expire-session-with-token="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_EXPIRE_SESSION_WITH_TOKEN="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.expire-session-with-token="..."

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

cas.authn.pac4j.oidc[0].generic.include-access-token-claims=

If enabled, try to process the access token as a JWT and include its claims in the profile. Only enable this if there is an agreement between the IdP and CAS about the format of the access token. If not, the token format could change at any time.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.include-access-token-claims=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          include-access-token-claims: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.include-access-token-claims="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_INCLUDE_ACCESS_TOKEN_CLAIMS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.include-access-token-claims="..."

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

cas.authn.pac4j.oidc[0].generic.logout-url=

Logout url used for this provider.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.logout-url=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          logout-url: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.logout-url="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_LOGOUT_URL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.logout-url="..."

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

cas.authn.pac4j.oidc[0].generic.mapped-claims=

List arbitrary mappings of claims when fetching user profiles. Uses a "directed list" where the allowed syntax would be claim->attribute.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.mapped-claims=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          mapped-claims: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.mapped-claims="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_MAPPED_CLAIMS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.mapped-claims="..."

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

cas.authn.pac4j.oidc[0].generic.max-clock-skew=

Clock skew in order to account for drift, when validating id tokens.

This settings supports the java.time.Duration syntax ^[?].

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.max-clock-skew=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          max-clock-skew: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.max-clock-skew="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_MAX_CLOCK_SKEW="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.max-clock-skew="..."

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

cas.authn.pac4j.oidc[0].generic.preferred-jws-algorithm=

The JWS algorithm to use forcefully when validating ID tokens. If none is defined, the first algorithm from metadata will be used.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.preferred-jws-algorithm=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          preferred-jws-algorithm: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.preferred-jws-algorithm="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_PREFERRED_JWS_ALGORITHM="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.preferred-jws-algorithm="..."

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

cas.authn.pac4j.oidc[0].generic.principal-id-attribute=

The attribute found in the identity provider response that may be used to establish the authenticated user and build a profile for CAS.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.principal-id-attribute=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          principal-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.authn.pac4j.oidc[0].generic.principal-id-attribute="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_PRINCIPAL_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.authn.pac4j.oidc[0].generic.principal-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.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.kid=

The key identifier.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.kid=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          private-key-jwt: 
            jwks: 
              kid: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.kid="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_PRIVATE_KEY_JWT_JWKS_KID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.kid="..."

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

cas.authn.pac4j.oidc[0].generic.read-timeout=

Connect timeout of the OIDC client.

This settings supports the java.time.Duration syntax ^[?].

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.read-timeout=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          read-timeout: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.read-timeout="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_READ_TIMEOUT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.read-timeout="..."

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

cas.authn.pac4j.oidc[0].generic.response-mode=

The response mode specifies how the result of the authorization request is formatted. For backward compatibility the default value is empty, which means the default pac4j (empty) response mode is used. Possible values includes "query", "fragment", "form_post", or "web_message"

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.response-mode=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          response-mode: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.response-mode="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_RESPONSE_MODE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.response-mode="..."

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

cas.authn.pac4j.oidc[0].generic.response-type=

The response type tells the authorization server which grant to execute. For backward compatibility the default value is empty, which means the default pac4j ("code") response type is used. Possibles values includes "code", "token" or "id_token".

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.response-type=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          response-type: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.response-type="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_RESPONSE_TYPE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.response-type="..."

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

cas.authn.pac4j.oidc[0].generic.scope=

Requested scope(s).

This setting supports the Spring Expression Language.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.scope=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          scope: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.scope="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_SCOPE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.scope="..."

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

cas.authn.pac4j.oidc[0].generic.supported-client-authentication-methods=

Control the list of supported client authentication methods that can be accepted and understood by this integration. Multiple methods may be specified and separated via a comma. Example might be client_secret_basic,client_secret_post,client_secret_jwt.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.supported-client-authentication-methods=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          supported-client-authentication-methods: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.supported-client-authentication-methods="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_SUPPORTED_CLIENT_AUTHENTICATION_METHODS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.supported-client-authentication-methods="..."

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

cas.authn.pac4j.oidc[0].generic.token-expiration-advance=

Default time period advance (in seconds) for considering an access token expired.

This settings supports the java.time.Duration syntax ^[?].

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.token-expiration-advance=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          token-expiration-advance: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.token-expiration-advance="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_TOKEN_EXPIRATION_ADVANCE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.token-expiration-advance="..."

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

cas.authn.pac4j.oidc[0].generic.use-nonce=

Whether an initial nonce should be to used initially for replay attack mitigation.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.use-nonce=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          use-nonce: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.use-nonce="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_USE_NONCE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.use-nonce="..."

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

cas.authn.pac4j.oidc[0].generic.validate-logout-token=

Controls whether the logout token submitted as a JWT should be validated for the correct signature, etc.

org.apereo.cas.configuration.model.support.pac4j.oidc.BasePac4jOidcClientProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.validate-logout-token=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          validate-logout-token: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.validate-logout-token="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_VALIDATE_LOGOUT_TOKEN="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.validate-logout-token="..."

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

# Whether unsigned id tokens issued as plain JWTs are accepted.
# cas.authn.pac4j.oidc[0].generic.allow-unsigned-id-tokens=

# Auto-redirect to this client.
# cas.authn.pac4j.oidc[0].generic.auto-redirect-type=NONE

# Callback URL to use to return the flow back to the CAS server one the identity provider is successfully done.
# cas.authn.pac4j.oidc[0].generic.callback-url=

# Determine how the callback url should be resolved.
# cas.authn.pac4j.oidc[0].generic.callback-url-type=QUERY_PARAMETER

# The preferred client authentication method that will be chosen for token requests.
# cas.authn.pac4j.oidc[0].generic.client-authentication-method=

# Name of the client mostly for UI purposes and uniqueness.
# cas.authn.pac4j.oidc[0].generic.client-name=

# Read timeout of the OIDC client.
# cas.authn.pac4j.oidc[0].generic.connect-timeout=

# CSS class that should be assigned to this client.
# cas.authn.pac4j.oidc[0].generic.css-class=

# Custom parameters to send along in authZ requests, etc.
# cas.authn.pac4j.oidc[0].generic.custom-params=

# Disable PKCE support for the provider.
# cas.authn.pac4j.oidc[0].generic.disable-pkce=

# Indicate the title or display name of the client for decoration and client presentation purposes.
# cas.authn.pac4j.oidc[0].generic.display-name=

# Whether the client/external identity provider should be considered active and enabled for integration purposes.
# cas.authn.pac4j.oidc[0].generic.enabled=true

# Checks if sessions expire with token expiration.
# cas.authn.pac4j.oidc[0].generic.expire-session-with-token=

# If enabled, try to process the access token as a JWT and include its claims in the profile.
# cas.authn.pac4j.oidc[0].generic.include-access-token-claims=

# Logout url used for this provider.
# cas.authn.pac4j.oidc[0].generic.logout-url=

# List arbitrary mappings of claims when fetching user profiles.
# cas.authn.pac4j.oidc[0].generic.mapped-claims=

# Clock skew in order to account for drift, when validating id tokens.
# cas.authn.pac4j.oidc[0].generic.max-clock-skew=

# The JWS algorithm to use forcefully when validating ID tokens.
# cas.authn.pac4j.oidc[0].generic.preferred-jws-algorithm=

# The attribute found in the identity provider response that may be used to establish the authenticated user and build a profile for CAS.
# cas.authn.pac4j.oidc[0].generic.principal-id-attribute=

# The key identifier.
# cas.authn.pac4j.oidc[0].generic.private-key-jwt.jwks.kid=

# Connect timeout of the OIDC client.
# cas.authn.pac4j.oidc[0].generic.read-timeout=

# The response mode specifies how the result of the authorization request is formatted.
# cas.authn.pac4j.oidc[0].generic.response-mode=

# The response type tells the authorization server which grant to execute.
# cas.authn.pac4j.oidc[0].generic.response-type=

# Requested scope(s).
# cas.authn.pac4j.oidc[0].generic.scope=

# Control the list of supported client authentication methods that can be accepted and understood by this integration.
# cas.authn.pac4j.oidc[0].generic.supported-client-authentication-methods=

# Default time period advance (in seconds) for considering an access token expired.
# cas.authn.pac4j.oidc[0].generic.token-expiration-advance=

# Whether an initial nonce should be to used initially for replay attack mitigation.
# cas.authn.pac4j.oidc[0].generic.use-nonce=

# Controls whether the logout token submitted as a JWT should be validated for the correct signature, etc.
# cas.authn.pac4j.oidc[0].generic.validate-logout-token=

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, especially 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.

Federation configuration

The federation nature of a delegated OIDC client must be explicitely enabled via CAS configuration.

Federation support translates into two aspects:

Exposing the entity statement of the OIDC client (The CAS server itself)
Resolving the trust chain to retrieve the target provider via the trust anchors.

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.location=

Specific JWKS for the federation. The location of the resource. Resources can be URLs, or files found either on the classpath or outside somewhere in the file system.

You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.location=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            jwks: 
              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.authn.pac4j.oidc[0].generic.federation.jwks.location="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_JWKS_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.authn.pac4j.oidc[0].generic.federation.jwks.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.authn.pac4j.oidc[0].generic.federation.application-type=web

Application type for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.application-type=web

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            application-type: "web"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.application-type="web" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_APPLICATION_TYPE="web"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.application-type="web"

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

cas.authn.pac4j.oidc[0].generic.federation.client-registration-types=explicit,automatic

Registration types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.client-registration-types=explicit,automatic

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            client-registration-types: "explicit,automatic"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.client-registration-types="explicit,automatic" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CLIENT_REGISTRATION_TYPES="explicit,automatic"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.client-registration-types="explicit,automatic"

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

cas.authn.pac4j.oidc[0].generic.federation.contact-emails=

The contact emails for this client.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.contact-emails=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            contact-emails: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.contact-emails="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CONTACT_EMAILS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.contact-emails="..."

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

cas.authn.pac4j.oidc[0].generic.federation.contact-name=

The contact name for this client.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.contact-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            contact-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.authn.pac4j.oidc[0].generic.federation.contact-name="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CONTACT_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.authn.pac4j.oidc[0].generic.federation.contact-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.authn.pac4j.oidc[0].generic.federation.enabled=

Whether the federation is enabled.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            enabled: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.enabled="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_ENABLED="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.enabled="..."

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

cas.authn.pac4j.oidc[0].generic.federation.grant-types=authorization_code

Grant types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.grant-types=authorization_code

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            grant-types: "authorization_code"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.grant-types="authorization_code" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_GRANT_TYPES="authorization_code"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.grant-types="authorization_code"

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.kid=

The key identifier.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.kid=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            jwks: 
              kid: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.jwks.kid="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_JWKS_KID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.jwks.kid="..."

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

cas.authn.pac4j.oidc[0].generic.federation.response-types=code

Response types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.response-types=code

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            response-types: "code"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.response-types="code" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_RESPONSE_TYPES="code"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.response-types="code"

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

cas.authn.pac4j.oidc[0].generic.federation.scopes=openid,email,profile

Scopes for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.scopes=openid,email,profile

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            scopes: "openid,email,profile"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.scopes="openid,email,profile" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_SCOPES="openid,email,profile"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.scopes="openid,email,profile"

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

cas.authn.pac4j.oidc[0].generic.federation.target-op=

The target OIDC provider in federation.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.target-op=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            target-op: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.target-op="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_TARGET_OP="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.target-op="..."

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

cas.authn.pac4j.oidc[0].generic.federation.trust-anchors=

The trust anchors to use for federation. This is defined as a map; the key is the trust anchor issuer and the value is the JWKS URL of the trust anchor.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.trust-anchors=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            trust-anchors: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.trust-anchors="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_TRUST_ANCHORS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.trust-anchors="..."

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

cas.authn.pac4j.oidc[0].generic.federation.validity-in-days=90

Validity in days of the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.validity-in-days=90

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            validity-in-days: "90"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.validity-in-days="90" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_VALIDITY_IN_DAYS="90"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.validity-in-days="90"

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

# Application type for the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.application-type=web

# Registration types for the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.client-registration-types=explicit,automatic

# The contact emails for this client.
# cas.authn.pac4j.oidc[0].generic.federation.contact-emails=

# The contact name for this client.
# cas.authn.pac4j.oidc[0].generic.federation.contact-name=

# Whether the federation is enabled.
# cas.authn.pac4j.oidc[0].generic.federation.enabled=

# Grant types for the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.grant-types=authorization_code

# The key identifier.
# cas.authn.pac4j.oidc[0].generic.federation.jwks.kid=

# Response types for the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.response-types=code

# Scopes for the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.scopes=openid,email,profile

# The target OIDC provider in federation.
# cas.authn.pac4j.oidc[0].generic.federation.target-op=

# The trust anchors to use for federation.
# cas.authn.pac4j.oidc[0].generic.federation.trust-anchors=

# Validity in days of the RP (client) entity statement.
# cas.authn.pac4j.oidc[0].generic.federation.validity-in-days=90

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

For exposing the entity statement, a JWKS must be defined as a resource (file or URL) with an optional key identifier. The entity statement is exposed on the /rp/{clientName}/.well-known/openid-federation URL of the CAS server.

For resolving the trust chain and authenticating on a target provider, the OP issuer must be defined as the targetOp property along with one or more trust anchors.

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.location=

Specific JWKS for the federation. The location of the resource. Resources can be URLs, or files found either on the classpath or outside somewhere in the file system.

You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.location=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            jwks: 
              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.authn.pac4j.oidc[0].generic.federation.jwks.location="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_JWKS_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.authn.pac4j.oidc[0].generic.federation.jwks.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.authn.pac4j.oidc[0].generic.federation.application-type=web

Application type for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.application-type=web

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            application-type: "web"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.application-type="web" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_APPLICATION_TYPE="web"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.application-type="web"

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

cas.authn.pac4j.oidc[0].generic.federation.client-registration-types=explicit,automatic

Registration types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.client-registration-types=explicit,automatic

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            client-registration-types: "explicit,automatic"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.client-registration-types="explicit,automatic" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CLIENT_REGISTRATION_TYPES="explicit,automatic"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.client-registration-types="explicit,automatic"

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

cas.authn.pac4j.oidc[0].generic.federation.contact-emails=

The contact emails for this client.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.contact-emails=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            contact-emails: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.contact-emails="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CONTACT_EMAILS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.contact-emails="..."

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

cas.authn.pac4j.oidc[0].generic.federation.contact-name=

The contact name for this client.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.contact-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            contact-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.authn.pac4j.oidc[0].generic.federation.contact-name="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_CONTACT_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.authn.pac4j.oidc[0].generic.federation.contact-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.authn.pac4j.oidc[0].generic.federation.enabled=

Whether the federation is enabled.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            enabled: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.enabled="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_ENABLED="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.enabled="..."

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

cas.authn.pac4j.oidc[0].generic.federation.grant-types=authorization_code

Grant types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.grant-types=authorization_code

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            grant-types: "authorization_code"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.grant-types="authorization_code" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_GRANT_TYPES="authorization_code"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.grant-types="authorization_code"

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.kid=

The key identifier.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientJwksProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.jwks.kid=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            jwks: 
              kid: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.jwks.kid="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_JWKS_KID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.jwks.kid="..."

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

cas.authn.pac4j.oidc[0].generic.federation.response-types=code

Response types for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.response-types=code

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            response-types: "code"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.response-types="code" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_RESPONSE_TYPES="code"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.response-types="code"

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

cas.authn.pac4j.oidc[0].generic.federation.scopes=openid,email,profile

Scopes for the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.scopes=openid,email,profile

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            scopes: "openid,email,profile"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.scopes="openid,email,profile" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_SCOPES="openid,email,profile"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.scopes="openid,email,profile"

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

cas.authn.pac4j.oidc[0].generic.federation.target-op=

The target OIDC provider in federation.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.target-op=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            target-op: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.target-op="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_TARGET_OP="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.target-op="..."

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

cas.authn.pac4j.oidc[0].generic.federation.trust-anchors=

The trust anchors to use for federation. This is defined as a map; the key is the trust anchor issuer and the value is the JWKS URL of the trust anchor.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.trust-anchors=...

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            trust-anchors: "..."

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.trust-anchors="..." -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_TRUST_ANCHORS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.trust-anchors="..."

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

cas.authn.pac4j.oidc[0].generic.federation.validity-in-days=90

Validity in days of the RP (client) entity statement.

org.apereo.cas.configuration.model.support.pac4j.oidc.Pac4jOidcClientFederationProperties.

_{How can I configure this property?}

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

Note

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

cas.authn.pac4j.oidc[0].generic.federation.validity-in-days=90

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      oidc[0]: 
        generic: 
          federation: 
            validity-in-days: "90"

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

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

java -Dcas.authn.pac4j.oidc[0].generic.federation.validity-in-days="90" -jar build/libs/cas.war

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

export CAS_AUTHN_PAC4J_OIDC[0]_GENERIC_FEDERATION_VALIDITY_IN_DAYS="90"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.authn.pac4j.oidc[0].generic.federation.validity-in-days="90"