Azure Active Directory

The discovery endpoint to locate the provider metadata.

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.

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.

The client id.

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.

The client secret.

Whether unsigned id tokens issued as plain JWTs are accepted.

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.

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.

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

Read timeout of the OIDC client.

CSS class that should be assigned to this client.

Custom parameters to send along in authZ requests, etc.

Disable PKCE support for the provider.

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.

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

Checks if sessions expire with token expiration.

Application type for the RP (client) entity statement.

Registration types for the RP (client) entity statement.

The contact emails for this client.

The contact name for this client.

Whether the federation is enabled.

Grant types for the RP (client) entity statement.

The key identifier.

Response types for the RP (client) entity statement.

Scopes for the RP (client) entity statement.

The target OIDC provider in federation.

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.

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

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.

Logout url used for this provider.

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

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

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

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

The key identifier.

Indicate whether the logout should be propagated from the CAS server to the delegated identity server.

Connect timeout of the OIDC client.

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"

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

Requested scope(s).

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.

Azure AD tenant name. After tenant is configured, #getDiscoveryUri() property will be overridden.

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

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

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