Azure Active Directory

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

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

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

cas.authn.pac4j.oidc[0].azure.discovery-uri=

The discovery endpoint to locate the provide metadata.

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

_{How can I configure this property?}

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

:information_source: 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].azure.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: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.id=

The client id.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.secret=

The client secret.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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. You should only include this field in your
configuration if you need to modify the default value.}

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

Whether unsigned id tokens issued as plain JWTs are accepted.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.auto-redirect-type=NONE

Auto-redirect to this client.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "NONE"          auto-redirect-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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "QUERY_PARAMETER"          callback-url-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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.connect-timeout=PT5S

Read timeout of the OIDC client.

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

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "PT5S"          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].azure.connect-timeout="PT5S" -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]_AZURE_CONNECT_TIMEOUT="PT5S"

java -jar build/libs/cas.war

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

CAS properties 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].azure.connect-timeout="PT5S"

The above example assumes that 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].azure.css-class=

CSS class that should be assigned to this client.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.custom-params=

Custom parameters to send along in authZ requests, etc.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.disable-pkce=

Disable PKCE support for the provider.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "true"          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].azure.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]_AZURE_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].azure.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].azure.expire-session-with-token=

Checks if sessions expire with token expiration.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.logout-url=

Logout url used for this provider.

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

_{How can I configure this property?}

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

:information_source: Note

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

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

CAS properties can be specified using the YAML syntax:

cas: 
  authn: 
    pac4j: 
      - oidc: 
        azure: "..."          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].azure.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]_AZURE_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].azure.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].azure.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.Pac4jAzureOidcClientProperties.

_{How can I configure this property?}

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

:information_source: Note

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