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.
LDAP Authentication
LDAP integration is enabled by including the following dependency in the overlay:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-ldap</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-ldap:${project.'cas.version'}"
1
2
3
4
5
6
7
8
9
dependencyManagement {
imports {
mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
}
}
dependencies {
implementation "org.apereo.cas:cas-server-support-ldap"
}
1
2
3
4
5
6
7
8
9
10
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-ldap"
}
Configuration
CAS authenticates a username/password against an LDAP directory such as Active Directory or OpenLDAP. There are numerous directory architectures and we provide configuration for four common cases.
Note that CAS will automatically create the appropriate components internally based on the settings specified below. If you wish to authenticate against more than one LDAP server, increment the index and specify the settings for the next LDAP server.
Note: Attributes retrieved as part of LDAP authentication are merged with all attributes retrieved from other attribute repository sources, if any. Attributes retrieved directly as part of LDAP authentication trump all other attributes.
The following settings and properties are available from the CAS configuration catalog:
- Required
- Optional
- Signing & Encryption
- Hibernate & JDBC
- Email Servers
- Groovy Scripting
- LDAP & Active Directory
- Authentication
- Password Encoding
- Principal Transformation
- Password Policy
- Notes
cas.authn.ldap[0].password-encoder.encoding-algorithm=
The encoding algorithm to use such as
CAS Property:
|
1 |
cas.authn.ldap[0].password-encoder.encoding-algorithm=... |
1
cas:
authn:
ldap[0]:
password-encoder:
encoding-algorithm: "..."
1
java -Dcas.authn.ldap[0].password-encoder.encoding-algorithm="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_ENCODING_ALGORITHM="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.encoding-algorithm="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.type=NONE
Define the password encoder type to use.
Type may be specified as blank or NONE
to disable password encoding.
It may also refer to a fully-qualified class name that implements
the Spring Security's PasswordEncoder
interface
if you wish you define your own encoder.
-
NONE
: No password encoding (i.e. plain-text) takes place. -
DEFAULT
: Use theDefaultPasswordEncoder
of CAS. For message-digest algorithms viacharacter-encoding
andencoding-algorithm
. -
BCRYPT
: Use theBCryptPasswordEncoder
based on the strength provided and an optional secret. -
SCRYPT
: Use theSCryptPasswordEncoder
. -
PBKDF2
: Use thePbkdf2PasswordEncoder
based on the strength provided and an optional secret. -
STANDARD
: Use theStandardPasswordEncoder
based on the secret provided. -
SSHA
: Use theLdapShaPasswordEncoder
supports Ldap SHA and SSHA (salted-SHA). The values are base-64 encoded and have the label {SHA} or {SSHA} prepended to the encoded hash. -
GLIBC_CRYPT
: Use theGlibcCryptPasswordEncoder
based on theencoding-algorithm
, strength provided and an optional secret. -
org.example.MyEncoder
: An implementation ofPasswordEncoder
of your own choosing. -
file:///path/to/script.groovy
: Path to a Groovy script charged with handling password encoding operations.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.type
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.type=NONE
1
cas:
authn:
ldap[0]:
password-encoder:
type: "NONE"
1
java -Dcas.authn.ldap[0].password-encoder.type="NONE" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_TYPE="NONE"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.type="NONE"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.groovy.location=
Handle password policy via Groovy script. 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, specially if the script set to reload on changes, you may need to adjust the total number ofinotify
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.SpringResourceProperties.
CAS Property: cas.authn.ldap[].password-policy.groovy.location
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.groovy.location=...
1
cas:
authn:
ldap[0]:
password-policy:
groovy:
location: "..."
1
java -Dcas.authn.ldap[0].password-policy.groovy.location="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_GROOVY_LOCATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.groovy.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.groovy.location=
Transform usernames using a Groovy resource. 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, specially if the script set to reload on changes, you may need to adjust the total number ofinotify
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.SpringResourceProperties.
CAS Property: cas.authn.ldap[].principal-transformation.groovy.location
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.groovy.location=...
1
cas:
authn:
ldap[0]:
principal-transformation:
groovy:
location: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.groovy.location="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_GROOVY_LOCATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.groovy.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].base-dn=
Base DN to use.
There may be scenarios where different parts of a single LDAP tree could be considered as base-dns. Rather than duplicating
the LDAP configuration block for each individual base-dn, each entry can be specified
and joined together using a special delimiter character. The user DN is retrieved using the combination of all base-dn and DN
resolvers in the order defined. DN resolution should fail if multiple DNs are found. Otherwise the first DN found is returned.
Usual syntax is: subtreeA,dc=example,dc=net|subtreeC,dc=example,dc=net
.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].base-dn
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.
.properties
files:
1
cas.authn.ldap[0].base-dn=...
1
cas:
authn:
ldap[0]:
base-dn: "..."
1
java -Dcas.authn.ldap[0].base-dn="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_BASE_DN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].base-dn="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].bind-credential=
The bind credential to use when connecting to LDAP.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].bind-credential
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.
.properties
files:
1
cas.authn.ldap[0].bind-credential=...
1
cas:
authn:
ldap[0]:
bind-credential: "..."
1
java -Dcas.authn.ldap[0].bind-credential="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_BIND_CREDENTIAL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].bind-credential="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].bind-dn=
The bind DN to use when connecting to LDAP. LDAP connection configuration injected into the LDAP connection pool can be initialized with the following parameters:
-
bindDn/bindCredential
provided - Use the provided credentials to bind when initializing connections. -
bindDn/bindCredential
set to*
- Use a fast-bind strategy to initialize the pool. -
bindDn/bindCredential
set to blank - Skip connection initializing; perform operations anonymously. - SASL mechanism provided - Use the given SASL mechanism to bind when initializing connections.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].bind-dn
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.
.properties
files:
1
cas.authn.ldap[0].bind-dn=...
1
cas:
authn:
ldap[0]:
bind-dn: "..."
1
java -Dcas.authn.ldap[0].bind-dn="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_BIND_DN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].bind-dn="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].ldap-url=
The LDAP url to the server. More than one may be specified, separated by space and/or comma.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].ldap-url
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.
.properties
files:
1
cas.authn.ldap[0].ldap-url=...
1
cas:
authn:
ldap[0]:
ldap-url: "..."
1
java -Dcas.authn.ldap[0].ldap-url="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_LDAP_URL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].ldap-url="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-filter=
User filter to use for searching.
Syntax is cn={user}
or cn={0}
.
file:/path/to/GroovyScript.groovy
to fully build the final filter template dynamically.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].search-filter
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.
.properties
files:
1
cas.authn.ldap[0].search-filter=...
1
cas:
authn:
ldap[0]:
search-filter: "..."
1
java -Dcas.authn.ldap[0].search-filter="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_FILTER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-filter="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].type=
The authentication type.
-
AD
- Users authenticate withsAMAccountName
. -
AUTHENTICATED
- Manager bind/search type of authentication. If {} principalAttributePassword} is empty then a user simple bind is done to validate credentials. Otherwise the given attribute is compared with the given
principalAttributePassword
using theSHA
encrypted value of it.</li>ANONYMOUS
: Similar semantics asAUTHENTICATED
except nobindDn
andbindCredential
may be specified to initialize the connection. IfprincipalAttributePassword
is empty then a user simple bind is done to validate credentials. Otherwise the given attribute is compared with the givenprincipalAttributePassword
using theSHA
encrypted value of it.- DIRECT: Direct Bind - Compute user DN from format string and perform simple bind. This is relevant when no search is required to compute the DN needed for a bind operation. Use cases for this type are: 1) All users are under a single branch in the directory,
</ul> Available values are as follows:e.g. ou=Users,dc=example,dc=org.
2) The username provided on the CAS login form is part of the DN, e.g.uid=%s,ou=Users,dc=example,dc=org
.-
AD
: Active Directory. -
AUTHENTICATED
: Authenticated Search. -
DIRECT
: Direct Bind. -
ANONYMOUS
: Anonymous Search.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property:
cas.authn.ldap[].type
Configuration properties can be included and activated using the following strategies.:information_source: NoteWhen 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: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.1
cas.authn.ldap[0].type=...
CAS properties can be specified using the YAML syntax:Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.1
cas:
authn:
ldap[0]:
type: "..."CAS properties can be passed to the CAS web application as system properties, when the application is launched:The above example assumes that the CAS web application is packaged as1
java -Dcas.authn.ldap[0].type="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in thebuild/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:The above example assumes that the CAS web application is packaged as1 2 3
export CAS_AUTHN_LDAP[0]_TYPE="..." java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in thebuild/libs
directory.CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:The above example assumes that the CAS web application is packaged as1
java -jar build/libs/cas.war --cas.authn.ldap[0].type="..."
cas.war
with an embedded server container and can be found in thebuild/libs
directory.
cas.authn.ldap=
Collection of settings related to LDAP authentication. These settings are required to be indexed (i.e. ldap[0].xyz).
CAS Property:
|
1 |
cas.authn.ldap=... |
1
cas:
authn:
ldap: "..."
1
java -Dcas.authn.ldap="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.character-encoding=UTF-8
The encoding algorithm to use such as 'UTF-8'.
Relevant when the type used is DEFAULT
.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.character-encoding
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.character-encoding=UTF-8
1
cas:
authn:
ldap[0]:
password-encoder:
character-encoding: "UTF-8"
1
java -Dcas.authn.ldap[0].password-encoder.character-encoding="UTF-8" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_CHARACTER_ENCODING="UTF-8"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.character-encoding="UTF-8"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.hash-length=16
When used by PasswordEncoderTypes#ARGON2
, it indicates the hash strength/length.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.hash-length
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.hash-length=16
1
cas:
authn:
ldap[0]:
password-encoder:
hash-length: "16"
1
java -Dcas.authn.ldap[0].password-encoder.hash-length="16" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_HASH_LENGTH="16"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.hash-length="16"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.iterations=310000
When used by PasswordEncoderTypes#PBKDF2
, it indicates the required number of iterations.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.iterations
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.iterations=310000
1
cas:
authn:
ldap[0]:
password-encoder:
iterations: "310000"
1
java -Dcas.authn.ldap[0].password-encoder.iterations="310000" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_ITERATIONS="310000"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.iterations="310000"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.secret=
Secret to use with PasswordEncoderTypes#STANDARD
, PasswordEncoderTypes#PBKDF2
,
PasswordEncoderTypes#BCRYPT
, PasswordEncoderTypes#GLIBC_CRYPT
password encoders.
Secret usually is an optional setting.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.secret
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.secret=...
1
cas:
authn:
ldap[0]:
password-encoder:
secret: "..."
1
java -Dcas.authn.ldap[0].password-encoder.secret="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_SECRET="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.secret="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.strength=16
Strength or number of iterations to use for password hashing.
Usually relevant when dealing with PasswordEncoderTypes#BCRYPT
, PasswordEncoderTypes#PBKDF2
or PasswordEncoderTypes#GLIBC_CRYPT
.
When used by PasswordEncoderTypes#ARGON2
or PasswordEncoderTypes#PBKDF2
, it indicates the salt strength.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.strength
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.strength=16
1
cas:
authn:
ldap[0]:
password-encoder:
strength: "16"
1
java -Dcas.authn.ldap[0].password-encoder.strength="16" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_STRENGTH="16"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.strength="16"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.blocking-pattern=
A regular expression that will be used against the username to match for blocking/forbidden values. If a match is found, an exception will be thrown and principal transformation will fail.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.blocking-pattern
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.blocking-pattern=...
1
cas:
authn:
ldap[0]:
principal-transformation:
blocking-pattern: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.blocking-pattern="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_BLOCKING_PATTERN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.blocking-pattern="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.case-conversion=NONE
Indicate whether the principal identifier should be transformed into upper-case, lower-case, etc. Available values are as follows:
-
NONE
: No conversion. -
LOWERCASE
: Lowercase conversion. -
UPPERCASE
: Uppercase conversion.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.case-conversion
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.case-conversion=NONE
1
cas:
authn:
ldap[0]:
principal-transformation:
case-conversion: "NONE"
1
java -Dcas.authn.ldap[0].principal-transformation.case-conversion="NONE" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_CASE_CONVERSION="NONE"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.case-conversion="NONE"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.pattern=
A regular expression that will be used against the provided username for username extractions. On a successful match, the first matched group in the pattern will be used as the extracted username.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.pattern
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.pattern=...
1
cas:
authn:
ldap[0]:
principal-transformation:
pattern: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.pattern="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_PATTERN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.pattern="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.prefix=
Prefix to add to the principal id prior to authentication.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.prefix
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.prefix=...
1
cas:
authn:
ldap[0]:
principal-transformation:
prefix: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.prefix="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_PREFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.suffix=
Suffix to add to the principal id prior to authentication.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.suffix
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.suffix=...
1
cas:
authn:
ldap[0]:
principal-transformation:
suffix: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.suffix="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.suffix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].additional-attributes=
List of additional attributes to retrieve, if any.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].additional-attributes
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.
.properties
files:
1
cas.authn.ldap[0].additional-attributes=...
1
cas:
authn:
ldap[0]:
additional-attributes: "..."
1
java -Dcas.authn.ldap[0].additional-attributes="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ADDITIONAL_ATTRIBUTES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].additional-attributes="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].allow-missing-principal-attribute-value=true
Flag to indicate whether CAS should block authentication if a specific/configured principal id attribute is not found.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].allow-missing-principal-attribute-value
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.
.properties
files:
1
cas.authn.ldap[0].allow-missing-principal-attribute-value=true
1
cas:
authn:
ldap[0]:
allow-missing-principal-attribute-value: "true"
1
java -Dcas.authn.ldap[0].allow-missing-principal-attribute-value="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ALLOW_MISSING_PRINCIPAL_ATTRIBUTE_VALUE="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].allow-missing-principal-attribute-value="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].allow-multiple-dns=
Whether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].allow-multiple-dns
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.
.properties
files:
1
cas.authn.ldap[0].allow-multiple-dns=...
1
cas:
authn:
ldap[0]:
allow-multiple-dns: "..."
1
java -Dcas.authn.ldap[0].allow-multiple-dns="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ALLOW_MULTIPLE_DNS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].allow-multiple-dns="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].allow-multiple-entries=
Set if multiple Entries are allowed.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].allow-multiple-entries
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.
.properties
files:
1
cas.authn.ldap[0].allow-multiple-entries=...
1
cas:
authn:
ldap[0]:
allow-multiple-entries: "..."
1
java -Dcas.authn.ldap[0].allow-multiple-entries="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ALLOW_MULTIPLE_ENTRIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].allow-multiple-entries="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].allow-multiple-principal-attribute-values=
Sets a flag that determines whether multiple values are allowed for the #principalAttributeId
.
This flag only has an effect if #principalAttributeId
is configured. If multiple values are detected
when the flag is false, the first value is used and a warning is logged. If multiple values are detected
when the flag is true, an exception is raised.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].allow-multiple-principal-attribute-values
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.
.properties
files:
1
cas.authn.ldap[0].allow-multiple-principal-attribute-values=...
1
cas:
authn:
ldap[0]:
allow-multiple-principal-attribute-values: "..."
1
java -Dcas.authn.ldap[0].allow-multiple-principal-attribute-values="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ALLOW_MULTIPLE_PRINCIPAL_ATTRIBUTE_VALUES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].allow-multiple-principal-attribute-values="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].binary-attributes=
Indicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].binary-attributes
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.
.properties
files:
1
cas.authn.ldap[0].binary-attributes=...
1
cas:
authn:
ldap[0]:
binary-attributes: "..."
1
java -Dcas.authn.ldap[0].binary-attributes="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_BINARY_ATTRIBUTES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].binary-attributes="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].block-wait-time=
The length of time the pool will block. By default the pool will block indefinitely and there is no guarantee that waiting threads will be serviced in the order in which they made their request. This option should be used with a blocking connection pool when you need to control the exact number of connections that can be created
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].block-wait-time
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.
.properties
files:
1
cas.authn.ldap[0].block-wait-time=...
1
cas:
authn:
ldap[0]:
block-wait-time: "..."
1
java -Dcas.authn.ldap[0].block-wait-time="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_BLOCK_WAIT_TIME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].block-wait-time="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].collect-dn-attribute=
When entry DN should be called as an attribute and stored into the principal.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].collect-dn-attribute
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.
.properties
files:
1
cas.authn.ldap[0].collect-dn-attribute=...
1
cas:
authn:
ldap[0]:
collect-dn-attribute: "..."
1
java -Dcas.authn.ldap[0].collect-dn-attribute="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_COLLECT_DN_ATTRIBUTE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].collect-dn-attribute="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].connect-timeout=
Sets the maximum amount of time that connects will block.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].connect-timeout
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.
.properties
files:
1
cas.authn.ldap[0].connect-timeout=...
1
cas:
authn:
ldap[0]:
connect-timeout: "..."
1
java -Dcas.authn.ldap[0].connect-timeout="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_CONNECT_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].connect-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].connection-strategy=
If multiple URLs are provided as the ldapURL this describes how each URL will be processed.
-
ACTIVE_PASSIVE
First LDAP will be used for every request unless it fails and then the next shall be used. -
ROUND_ROBIN
For each new connection the next url in the list will be used. -
RANDOM
For each new connection a random LDAP url will be selected. -
DNS_SRV
LDAP urls based on DNS SRV records of the configured/given LDAP url will be used.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].connection-strategy
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.
.properties
files:
1
cas.authn.ldap[0].connection-strategy=...
1
cas:
authn:
ldap[0]:
connection-strategy: "..."
1
java -Dcas.authn.ldap[0].connection-strategy="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_CONNECTION_STRATEGY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].connection-strategy="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].credential-criteria=
A number of authentication handlers are allowed to determine whether they can operate on the provided credential and as such lend themselves to be tried and tested during the authentication handler selection phase. The credential criteria may be one of the following options:
- 1) A regular expression pattern that is tested against the credential identifier.
- 2) A fully qualified class name of your own design that implements
Predicate
. - 3) Path to an external Groovy script that implements the same interface.
This settings supports regular expression patterns. [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].credential-criteria
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.
.properties
files:
1
cas.authn.ldap[0].credential-criteria=...
1
cas:
authn:
ldap[0]:
credential-criteria: "..."
1
java -Dcas.authn.ldap[0].credential-criteria="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_CREDENTIAL_CRITERIA="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].credential-criteria="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].deref-aliases=
Define how aliases are de-referenced. Accepted values are:
NEVER
-
SEARCHING
: dereference when searching the entries beneath the starting point but not when searching for the starting entry. -
FINDING
: dereference when searching for the starting entry but not when searching the entries beneath the starting point. -
ALWAYS
: dereference when searching for the starting entry and when searching the entries beneath the starting point.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].deref-aliases
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.
.properties
files:
1
cas.authn.ldap[0].deref-aliases=...
1
cas:
authn:
ldap[0]:
deref-aliases: "..."
1
java -Dcas.authn.ldap[0].deref-aliases="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_DEREF_ALIASES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].deref-aliases="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].disable-pooling=
Whether to use a pooled connection factory in components.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].disable-pooling
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.
.properties
files:
1
cas.authn.ldap[0].disable-pooling=...
1
cas:
authn:
ldap[0]:
disable-pooling: "..."
1
java -Dcas.authn.ldap[0].disable-pooling="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_DISABLE_POOLING="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].disable-pooling="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].dn-format=
Specify the dn format accepted by the AD authenticator, etc.
Example format might be uid=%s,ou=people,dc=example,dc=org
.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].dn-format
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.
.properties
files:
1
cas.authn.ldap[0].dn-format=...
1
cas:
authn:
ldap[0]:
dn-format: "..."
1
java -Dcas.authn.ldap[0].dn-format="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_DN_FORMAT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].dn-format="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].enhance-with-entry-resolver=
Whether specific search entry resolvers need to be set on the authenticator, or the default should be used.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].enhance-with-entry-resolver
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.
.properties
files:
1
cas.authn.ldap[0].enhance-with-entry-resolver=...
1
cas:
authn:
ldap[0]:
enhance-with-entry-resolver: "..."
1
java -Dcas.authn.ldap[0].enhance-with-entry-resolver="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ENHANCE_WITH_ENTRY_RESOLVER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].enhance-with-entry-resolver="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].fail-fast=
Attempt to populate the connection pool early on startup and fail quickly if something goes wrong.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].fail-fast
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.
.properties
files:
1
cas.authn.ldap[0].fail-fast=...
1
cas:
authn:
ldap[0]:
fail-fast: "..."
1
java -Dcas.authn.ldap[0].fail-fast="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_FAIL_FAST="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].fail-fast="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].follow-referrals=
Set if search referrals should be followed.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].follow-referrals
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.
.properties
files:
1
cas.authn.ldap[0].follow-referrals=...
1
cas:
authn:
ldap[0]:
follow-referrals: "..."
1
java -Dcas.authn.ldap[0].follow-referrals="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_FOLLOW_REFERRALS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].follow-referrals="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].hostname-verifier=
Hostname verification options. Available values are as follows:
-
DEFAULT
: Default option, forcing verification. -
ANY
: Skip hostname verification and allow all.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].hostname-verifier
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.
.properties
files:
1
cas.authn.ldap[0].hostname-verifier=...
1
cas:
authn:
ldap[0]:
hostname-verifier: "..."
1
java -Dcas.authn.ldap[0].hostname-verifier="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_HOSTNAME_VERIFIER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].hostname-verifier="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].idle-time=
Removes connections from the pool based on how long they have been idle in the available queue. Prunes connections that have been idle for more than the indicated amount.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].idle-time
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.
.properties
files:
1
cas.authn.ldap[0].idle-time=...
1
cas:
authn:
ldap[0]:
idle-time: "..."
1
java -Dcas.authn.ldap[0].idle-time="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_IDLE_TIME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].idle-time="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].keystore=
Path to the keystore used for SSL connections. Typically contains SSL certificates for the LDAP server.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].keystore
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.
.properties
files:
1
cas.authn.ldap[0].keystore=...
1
cas:
authn:
ldap[0]:
keystore: "..."
1
java -Dcas.authn.ldap[0].keystore="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_KEYSTORE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].keystore="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].keystore-password=
Keystore password.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].keystore-password
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.
.properties
files:
1
cas.authn.ldap[0].keystore-password=...
1
cas:
authn:
ldap[0]:
keystore-password: "..."
1
java -Dcas.authn.ldap[0].keystore-password="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_KEYSTORE_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].keystore-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].keystore-type=
The type of keystore. PKCS12
or JKS
.
If left blank, defaults to the default keystore type indicated
by the underlying Java platform.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].keystore-type
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.
.properties
files:
1
cas.authn.ldap[0].keystore-type=...
1
cas:
authn:
ldap[0]:
keystore-type: "..."
1
java -Dcas.authn.ldap[0].keystore-type="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_KEYSTORE_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].keystore-type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].max-pool-size=
Maximum LDAP connection pool size which the pool can use to grow.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].max-pool-size
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.
.properties
files:
1
cas.authn.ldap[0].max-pool-size=...
1
cas:
authn:
ldap[0]:
max-pool-size: "..."
1
java -Dcas.authn.ldap[0].max-pool-size="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_MAX_POOL_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].max-pool-size="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].min-pool-size=
Minimum LDAP connection pool size. Size the pool should be initialized to and pruned to
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].min-pool-size
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.
.properties
files:
1
cas.authn.ldap[0].min-pool-size=...
1
cas:
authn:
ldap[0]:
min-pool-size: "..."
1
java -Dcas.authn.ldap[0].min-pool-size="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_MIN_POOL_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].min-pool-size="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].name=
Name of the LDAP handler.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].name
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.
.properties
files:
1
cas.authn.ldap[0].name=...
1
cas:
authn:
ldap[0]:
name: "..."
1
java -Dcas.authn.ldap[0].name="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].order=
Order of the authentication handler in the chain.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].order
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.
.properties
files:
1
cas.authn.ldap[0].order=...
1
cas:
authn:
ldap[0]:
order: "..."
1
java -Dcas.authn.ldap[0].order="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_ORDER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].page-size=
Request that the server return results in batches of a specific size. See RFC 2696. This control is often used to work around server result size limits. A negative/zero value disables paged requests.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].page-size
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.
.properties
files:
1
cas.authn.ldap[0].page-size=...
1
cas:
authn:
ldap[0]:
page-size: "..."
1
java -Dcas.authn.ldap[0].page-size="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PAGE_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].page-size="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.account-state-handling-enabled=true
Indicates whether account state handling should be enabled to process warnings or errors reported back from the authentication response, produced by the source.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.account-state-handling-enabled
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.account-state-handling-enabled=true
1
cas:
authn:
ldap[0]:
password-policy:
account-state-handling-enabled: "true"
1
java -Dcas.authn.ldap[0].password-policy.account-state-handling-enabled="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_ACCOUNT_STATE_HANDLING_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.account-state-handling-enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.custom-policy-class=
An implementation of a policy class that knows how to handle LDAP responses.
The class must be an implementation of org.ldaptive.auth.AuthenticationResponseHandler
.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.custom-policy-class
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.custom-policy-class=...
1
cas:
authn:
ldap[0]:
password-policy:
custom-policy-class: "..."
1
java -Dcas.authn.ldap[0].password-policy.custom-policy-class="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_CUSTOM_POLICY_CLASS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.custom-policy-class="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.display-warning-on-match=true
Indicates if warning should be displayed, when the ldap attribute value
matches the #warningAttributeValue
.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.display-warning-on-match
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.display-warning-on-match=true
1
cas:
authn:
ldap[0]:
password-policy:
display-warning-on-match: "true"
1
java -Dcas.authn.ldap[0].password-policy.display-warning-on-match="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_DISPLAY_WARNING_ON_MATCH="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.display-warning-on-match="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.enabled=true
Whether password policy should be enabled.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.enabled
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.enabled=true
1
cas:
authn:
ldap[0]:
password-policy:
enabled: "true"
1
java -Dcas.authn.ldap[0].password-policy.enabled="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.login-failures=5
When dealing with FreeIPA, indicates the number of allows login failures.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.login-failures
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.login-failures=5
1
cas:
authn:
ldap[0]:
password-policy:
login-failures: "5"
1
java -Dcas.authn.ldap[0].password-policy.login-failures="5" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_LOGIN_FAILURES="5"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.login-failures="5"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.password-expiration-number-of-days=180
This is used to calculate an expiration period for the account password.
When defined, LDAP password policy handling will use the pwdLastSet
attribute
which must be returned from the LDAP authentication attempt.
LDAP password policy handling will emit a warning for the pwdLastSet
value plus the expiration amount.
A negative value will disable the operations that calculate the expiration period.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.password-expiration-number-of-days
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.password-expiration-number-of-days=180
1
cas:
authn:
ldap[0]:
password-policy:
password-expiration-number-of-days: "180"
1
java -Dcas.authn.ldap[0].password-policy.password-expiration-number-of-days="180" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_PASSWORD_EXPIRATION_NUMBER_OF_DAYS="180"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.password-expiration-number-of-days="180"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.policy-attributes=
Key-value structure (Map) that indicates a list of boolean attributes as keys.
If either attribute value is true, indicating an account state is flagged,
the corresponding error can be thrown.
Example accountLocked=javax.security.auth.login.AccountLockedException
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.policy-attributes
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.policy-attributes=...
1
cas:
authn:
ldap[0]:
password-policy:
policy-attributes: "..."
1
java -Dcas.authn.ldap[0].password-policy.policy-attributes="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_POLICY_ATTRIBUTES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.policy-attributes="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.strategy=DEFAULT
Decide how authentication should handle password policy changes. Available values are as follows:
-
DEFAULT
: Default option to handle policy changes. -
GROOVY
: Handle account password policies via Groovy. -
REJECT_RESULT_CODE
: Strategy to only activate password policy if the authentication response code is not blocked.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.strategy
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.strategy=DEFAULT
1
cas:
authn:
ldap[0]:
password-policy:
strategy: "DEFAULT"
1
java -Dcas.authn.ldap[0].password-policy.strategy="DEFAULT" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_STRATEGY="DEFAULT"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.strategy="DEFAULT"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.type=GENERIC
LDAP type.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.type
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.type=GENERIC
1
cas:
authn:
ldap[0]:
password-policy:
type: "GENERIC"
1
java -Dcas.authn.ldap[0].password-policy.type="GENERIC" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_TYPE="GENERIC"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.type="GENERIC"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warn-all=
Always display the password expiration warning regardless.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warn-all
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warn-all=...
1
cas:
authn:
ldap[0]:
password-policy:
warn-all: "..."
1
java -Dcas.authn.ldap[0].password-policy.warn-all="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARN_ALL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warn-all="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-attribute-name=
Used by an account state handling policy that only calculates account warnings in case the entry carries this attribute.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-attribute-name=...
1
cas:
authn:
ldap[0]:
password-policy:
warning-attribute-name: "..."
1
java -Dcas.authn.ldap[0].password-policy.warning-attribute-name="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_ATTRIBUTE_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-attribute-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-attribute-value=
Used by an account state handling policy that only calculates account warnings
in case the entry carries an attribute #warningAttributeName
whose value matches this field.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-attribute-value
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-attribute-value=...
1
cas:
authn:
ldap[0]:
password-policy:
warning-attribute-value: "..."
1
java -Dcas.authn.ldap[0].password-policy.warning-attribute-value="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_ATTRIBUTE_VALUE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-attribute-value="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-days=30
This is used to calculate a warning period to see if account expiry is within the calculated window.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-days
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-days=30
1
cas:
authn:
ldap[0]:
password-policy:
warning-days: "30"
1
java -Dcas.authn.ldap[0].password-policy.warning-days="30" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_DAYS="30"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-days="30"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].pool-passivator=
You may receive unexpected LDAP failures, when CAS is configured to authenticate
using DIRECT
or AUTHENTICATED
types and LDAP is locked down to not allow anonymous binds/searches.
Every second attempt with a given LDAP connection from the pool would fail if it was on
the same connection as a failed login attempt, and the regular connection validator would
similarly fail. When a connection is returned back to a pool,
it still may contain the principal and credentials from the previous attempt.
Before the next bind attempt using that connection, the validator tries to
validate the connection again but fails because it’s no longer trying with the
configured bind credentials but with whatever user DN was used in the previous step.
Given the validation failure, the connection is closed and CAS would deny
access by default. Passivators attempt to reconnect
to LDAP with the configured bind credentials, effectively resetting the connection
to what it should be after each bind request.
Furthermore if you are seeing errors in the logs that resemble
a 'Operation exception encountered, reopening connection' type of message, this
usually is an indication that the connection pool’s validation timeout
established and created by CAS is greater than the timeout configured
in the LDAP server, or more likely, in the load balancer in front of
the LDAP servers. You can adjust the LDAP server session’s timeout
for connections, or you can teach CAS to use a validity period that
is equal or less than the LDAP server session’s timeout.
Accepted values are:
-
NONE
: No passivation takes place. -
BIND
: The default behavior which passivates a connection by performing a bind operation on it. This option requires the availability of bind credentials when establishing connections to LDAP.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].pool-passivator
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.
.properties
files:
1
cas.authn.ldap[0].pool-passivator=...
1
cas:
authn:
ldap[0]:
pool-passivator: "..."
1
java -Dcas.authn.ldap[0].pool-passivator="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_POOL_PASSIVATOR="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].pool-passivator="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-attribute-id=
The attribute to use as the principal identifier built during and upon a successful authentication attempt.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].principal-attribute-id
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.
.properties
files:
1
cas.authn.ldap[0].principal-attribute-id=...
1
cas:
authn:
ldap[0]:
principal-attribute-id: "..."
1
java -Dcas.authn.ldap[0].principal-attribute-id="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_ATTRIBUTE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-attribute-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-attribute-list=
List of attributes to retrieve from LDAP.
Attributes can be virtually remapped to multiple names.
Example cn:commonName,givenName,eduPersonTargettedId:SOME_IDENTIFIER
.
homePostalAddress:homePostalAddress;
.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].principal-attribute-list
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.
.properties
files:
1
cas.authn.ldap[0].principal-attribute-list=...
1
cas:
authn:
ldap[0]:
principal-attribute-list: "..."
1
java -Dcas.authn.ldap[0].principal-attribute-list="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_ATTRIBUTE_LIST="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-attribute-list="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-attribute-password=
If principalAttributePassword is empty then a user simple bind is done to validate credentials otherwise the given attribute is compared with the given principalAttributePassword using the SHA encrypted value of it.
For the anonymous authentication type, if principalAttributePassword is empty then a user simple bind is done to validate credentials otherwise the given attribute is compared with the given principalAttributePassword using the SHA encrypted value of it. org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].principal-attribute-password
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.
.properties
files:
1
cas.authn.ldap[0].principal-attribute-password=...
1
cas:
authn:
ldap[0]:
principal-attribute-password: "..."
1
java -Dcas.authn.ldap[0].principal-attribute-password="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_ATTRIBUTE_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-attribute-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-dn-attribute-name=principalLdapDn
Name of attribute to be used for principal's DN.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].principal-dn-attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].principal-dn-attribute-name=principalLdapDn
1
cas:
authn:
ldap[0]:
principal-dn-attribute-name: "principalLdapDn"
1
java -Dcas.authn.ldap[0].principal-dn-attribute-name="principalLdapDn" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_DN_ATTRIBUTE_NAME="principalLdapDn"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-dn-attribute-name="principalLdapDn"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].prune-period=
Removes connections from the pool based on how long they have been idle in the available queue. Run the pruning process at the indicated interval.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].prune-period
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.
.properties
files:
1
cas.authn.ldap[0].prune-period=...
1
cas:
authn:
ldap[0]:
prune-period: "..."
1
java -Dcas.authn.ldap[0].prune-period="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRUNE_PERIOD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].prune-period="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].resolve-from-attribute=
If this attribute is set, the value found in the first attribute value will be used in place of the DN.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].resolve-from-attribute
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.
.properties
files:
1
cas.authn.ldap[0].resolve-from-attribute=...
1
cas:
authn:
ldap[0]:
resolve-from-attribute: "..."
1
java -Dcas.authn.ldap[0].resolve-from-attribute="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_RESOLVE_FROM_ATTRIBUTE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].resolve-from-attribute="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].response-timeout=
Duration of time to wait for responses.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].response-timeout
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.
.properties
files:
1
cas.authn.ldap[0].response-timeout=...
1
cas:
authn:
ldap[0]:
response-timeout: "..."
1
java -Dcas.authn.ldap[0].response-timeout="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_RESPONSE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].response-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-authorization-id=
SASL authorization id.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-authorization-id
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.
.properties
files:
1
cas.authn.ldap[0].sasl-authorization-id=...
1
cas:
authn:
ldap[0]:
sasl-authorization-id: "..."
1
java -Dcas.authn.ldap[0].sasl-authorization-id="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_AUTHORIZATION_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-authorization-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-mechanism=
The SASL mechanism.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-mechanism
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.
.properties
files:
1
cas.authn.ldap[0].sasl-mechanism=...
1
cas:
authn:
ldap[0]:
sasl-mechanism: "..."
1
java -Dcas.authn.ldap[0].sasl-mechanism="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_MECHANISM="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-mechanism="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-mutual-auth=
SASL mutual auth is enabled?
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-mutual-auth
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.
.properties
files:
1
cas.authn.ldap[0].sasl-mutual-auth=...
1
cas:
authn:
ldap[0]:
sasl-mutual-auth: "..."
1
java -Dcas.authn.ldap[0].sasl-mutual-auth="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_MUTUAL_AUTH="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-mutual-auth="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-quality-of-protection=
SASL quality of protected.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-quality-of-protection
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.
.properties
files:
1
cas.authn.ldap[0].sasl-quality-of-protection=...
1
cas:
authn:
ldap[0]:
sasl-quality-of-protection: "..."
1
java -Dcas.authn.ldap[0].sasl-quality-of-protection="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_QUALITY_OF_PROTECTION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-quality-of-protection="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-realm=
The SASL realm.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-realm
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.
.properties
files:
1
cas.authn.ldap[0].sasl-realm=...
1
cas:
authn:
ldap[0]:
sasl-realm: "..."
1
java -Dcas.authn.ldap[0].sasl-realm="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_REALM="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-realm="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].sasl-security-strength=
SASL security strength.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].sasl-security-strength
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.
.properties
files:
1
cas.authn.ldap[0].sasl-security-strength=...
1
cas:
authn:
ldap[0]:
sasl-security-strength: "..."
1
java -Dcas.authn.ldap[0].sasl-security-strength="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SASL_SECURITY_STRENGTH="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].sasl-security-strength="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-name-case-change=
The Attribute name case change.
org.apereo.cas.configuration.model.support.ldap.CaseChangeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.case-change.attribute-name-case-change
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-name-case-change=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
case-change:
attribute-name-case-change: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.case-change.attribute-name-case-change="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_CASE_CHANGE_ATTRIBUTE_NAME_CASE_CHANGE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.case-change.attribute-name-case-change="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-names=
The Attribute names.
org.apereo.cas.configuration.model.support.ldap.CaseChangeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.case-change.attribute-names
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-names=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
case-change:
attribute-names: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.case-change.attribute-names="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_CASE_CHANGE_ATTRIBUTE_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.case-change.attribute-names="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-value-case-change=
The Attribute value case change.
org.apereo.cas.configuration.model.support.ldap.CaseChangeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.case-change.attribute-value-case-change
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.case-change.attribute-value-case-change=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
case-change:
attribute-value-case-change: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.case-change.attribute-value-case-change="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_CASE_CHANGE_ATTRIBUTE_VALUE_CASE_CHANGE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.case-change.attribute-value-case-change="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.case-change.dn-case-change=
The Dn case change.
org.apereo.cas.configuration.model.support.ldap.CaseChangeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.case-change.dn-case-change
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.case-change.dn-case-change=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
case-change:
dn-case-change: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.case-change.dn-case-change="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_CASE_CHANGE_DN_CASE_CHANGE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.case-change.dn-case-change="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.dn-attribute.add-if-exists=
The Add if exists.
org.apereo.cas.configuration.model.support.ldap.DnAttributeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.dn-attribute.add-if-exists
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.dn-attribute.add-if-exists=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
dn-attribute:
add-if-exists: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.dn-attribute.add-if-exists="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_DN_ATTRIBUTE_ADD_IF_EXISTS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.dn-attribute.add-if-exists="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.dn-attribute.dn-attribute-name=entryDN
The Dn attribute name.
org.apereo.cas.configuration.model.support.ldap.DnAttributeSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.dn-attribute.dn-attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.dn-attribute.dn-attribute-name=entryDN
1
cas:
authn:
ldap[0]:
search-entry-handlers:
dn-attribute:
dn-attribute-name: "entryDN"
1
java -Dcas.authn.ldap[0].search-entry-handlers.dn-attribute.dn-attribute-name="entryDN" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_DN_ATTRIBUTE_DN_ATTRIBUTE_NAME="entryDN"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.dn-attribute.dn-attribute-name="entryDN"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.merge-attribute.attribute-names=
The Attribute names.
org.apereo.cas.configuration.model.support.ldap.MergeAttributesSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.merge-attribute.attribute-names
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.merge-attribute.attribute-names=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
merge-attribute:
attribute-names: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.merge-attribute.attribute-names="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_MERGE_ATTRIBUTE_ATTRIBUTE_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.merge-attribute.attribute-names="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.merge-attribute.merge-attribute-name=
The Merge attribute name.
org.apereo.cas.configuration.model.support.ldap.MergeAttributesSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.merge-attribute.merge-attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.merge-attribute.merge-attribute-name=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
merge-attribute:
merge-attribute-name: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.merge-attribute.merge-attribute-name="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_MERGE_ATTRIBUTE_MERGE_ATTRIBUTE_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.merge-attribute.merge-attribute-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.primary-group-id.base-dn=
The Base dn.
org.apereo.cas.configuration.model.support.ldap.PrimaryGroupIdSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.primary-group-id.base-dn
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.primary-group-id.base-dn=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
primary-group-id:
base-dn: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.primary-group-id.base-dn="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_PRIMARY_GROUP_ID_BASE_DN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.primary-group-id.base-dn="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.primary-group-id.group-filter=(&(objectClass=group)(objectSid={0}))
The Group filter.
org.apereo.cas.configuration.model.support.ldap.PrimaryGroupIdSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.primary-group-id.group-filter
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.primary-group-id.group-filter=(&(objectClass=group)(objectSid={0}))
1
cas:
authn:
ldap[0]:
search-entry-handlers:
primary-group-id:
group-filter: "(&(objectClass=group)(objectSid={0}))"
1
java -Dcas.authn.ldap[0].search-entry-handlers.primary-group-id.group-filter="(&(objectClass=group)(objectSid={0}))" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_PRIMARY_GROUP_ID_GROUP_FILTER="(&(objectClass=group)(objectSid={0}))"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.primary-group-id.group-filter="(&(objectClass=group)(objectSid={0}))"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.recursive.merge-attributes=
The Merge attributes.
org.apereo.cas.configuration.model.support.ldap.RecursiveSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.recursive.merge-attributes
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.recursive.merge-attributes=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
recursive:
merge-attributes: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.recursive.merge-attributes="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_RECURSIVE_MERGE_ATTRIBUTES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.recursive.merge-attributes="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.recursive.search-attribute=
The Search attribute.
org.apereo.cas.configuration.model.support.ldap.RecursiveSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.recursive.search-attribute
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.recursive.search-attribute=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
recursive:
search-attribute: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.recursive.search-attribute="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_RECURSIVE_SEARCH_ATTRIBUTE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.recursive.search-attribute="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.search-referral.limit=10
The default referral limit.
org.apereo.cas.configuration.model.support.ldap.FollowReferralSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.search-referral.limit
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.search-referral.limit=10
1
cas:
authn:
ldap[0]:
search-entry-handlers:
search-referral:
limit: "10"
1
java -Dcas.authn.ldap[0].search-entry-handlers.search-referral.limit="10" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_SEARCH_REFERRAL_LIMIT="10"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.search-referral.limit="10"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.search-result.limit=10
The default referral limit.
org.apereo.cas.configuration.model.support.ldap.FollowResultSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.search-result.limit
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.search-result.limit=10
1
cas:
authn:
ldap[0]:
search-entry-handlers:
search-result:
limit: "10"
1
java -Dcas.authn.ldap[0].search-entry-handlers.search-result.limit="10" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_SEARCH_RESULT_LIMIT="10"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.search-result.limit="10"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].search-entry-handlers.type=
The type of search entry handler to choose. Available values are as follows:
-
FOLLOW_SEARCH_REFERRAL
: Provides handling of an ldap referral for search operations. -
FOLLOW_SEARCH_RESULT_REFERENCE
: Provides handling of an ldap continuation reference for search operations. -
ACTIVE_DIRECTORY
: Process the entry results fetched from active directory and check for account status controls for disabled/expired accounts, etc. -
OBJECT_GUID
: Object guid search entry handler. Handles theobjectGUID
attribute fetching and conversion. -
OBJECT_SID
: Object sid search entry handler. Handles theobjectSid
attribute fetching and conversion. -
CASE_CHANGE
: Case change search entry handler. Provides the ability to modify the case of search entry DNs, attribute names, and attribute values. -
DN_ATTRIBUTE_ENTRY
: DN attribute entry handler. Adds the entry DN as an attribute to the result set. Provides a client side implementation of RFC 5020. -
MERGE
: Merge search entry handler. Merges the values of one or more attributes into a single attribute. -
PRIMARY_GROUP
: Primary group search handler. Constructs the primary group SID and then searches for that group and puts it's DN in thememberOf
attribute of the original search entry. -
RANGE_ENTRY
: Range entry search handler. Rewrites attributes returned from Active Directory to include all values by performing additional searches. -
RECURSIVE_ENTRY
: Recursive entry search handler. This recursively searches based on a supplied attribute and merges those results into the original entry. -
MERGE_ENTRIES
: Merge entries handler. Merges the values of one or more attributes in all entries into a single attribute. The merged attribute may or may not already exist on the entry. If it does exist it's existing values will remain intact.
org.apereo.cas.configuration.model.support.ldap.LdapSearchEntryHandlersProperties.
CAS Property: cas.authn.ldap[].search-entry-handlers.type
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.
.properties
files:
1
cas.authn.ldap[0].search-entry-handlers.type=...
1
cas:
authn:
ldap[0]:
search-entry-handlers:
type: "..."
1
java -Dcas.authn.ldap[0].search-entry-handlers.type="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SEARCH_ENTRY_HANDLERS_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].search-entry-handlers.type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].state=ACTIVE
Define the scope and state of this authentication handler and the lifecycle in which it can be invoked or activated. Available values are as follows:
-
ACTIVE
: Active authentication handler, and is invoked by default automatically to verify credentials globally. -
STANDBY
: Authentication handler is in a semi-enabled state, waiting to be called only on-demand when explicitly asked for.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].state
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.
.properties
files:
1
cas.authn.ldap[0].state=ACTIVE
1
cas:
authn:
ldap[0]:
state: "ACTIVE"
1
java -Dcas.authn.ldap[0].state="ACTIVE" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_STATE="ACTIVE"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].state="ACTIVE"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].subtree-search=
Whether subtree searching is allowed.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].subtree-search
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.
.properties
files:
1
cas.authn.ldap[0].subtree-search=...
1
cas:
authn:
ldap[0]:
subtree-search: "..."
1
java -Dcas.authn.ldap[0].subtree-search="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_SUBTREE_SEARCH="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].subtree-search="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].trust-certificates=
Path of the trust certificates to use for the SSL connection. Ignores keystore-related settings when activated and used.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].trust-certificates
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.
.properties
files:
1
cas.authn.ldap[0].trust-certificates=...
1
cas:
authn:
ldap[0]:
trust-certificates: "..."
1
java -Dcas.authn.ldap[0].trust-certificates="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_TRUST_CERTIFICATES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].trust-certificates="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].trust-manager=
Trust Manager options. Trust managers are responsible for managing the trust material that is used when making LDAP trust decisions, and for deciding whether credentials presented by a peer should be accepted. Accepted values are: *
-
DEFAULT
: Enable and force the default JVM trust managers. -
ANY
: Trust any client or server.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].trust-manager
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.
.properties
files:
1
cas.authn.ldap[0].trust-manager=...
1
cas:
authn:
ldap[0]:
trust-manager: "..."
1
java -Dcas.authn.ldap[0].trust-manager="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_TRUST_MANAGER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].trust-manager="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].trust-store=
Path to the keystore used to determine which certificates or certificate authorities should be trusted. Used when connecting to an LDAP server via LDAPS or startTLS connection. If left blank, the default truststore for the Java runtime is used.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].trust-store
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.
.properties
files:
1
cas.authn.ldap[0].trust-store=...
1
cas:
authn:
ldap[0]:
trust-store: "..."
1
java -Dcas.authn.ldap[0].trust-store="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_TRUST_STORE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].trust-store="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].trust-store-password=
Password needed to open the truststore.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].trust-store-password
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.
.properties
files:
1
cas.authn.ldap[0].trust-store-password=...
1
cas:
authn:
ldap[0]:
trust-store-password: "..."
1
java -Dcas.authn.ldap[0].trust-store-password="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_TRUST_STORE_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].trust-store-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].trust-store-type=
The type of trust keystore that determines which certificates or certificate authorities are trusted.
Types depend on underlying java platform, typically PKCS12
or JKS
.
If left blank, defaults to the default keystore type indicated
by the underlying Java platform.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].trust-store-type
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.
.properties
files:
1
cas.authn.ldap[0].trust-store-type=...
1
cas:
authn:
ldap[0]:
trust-store-type: "..."
1
java -Dcas.authn.ldap[0].trust-store-type="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_TRUST_STORE_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].trust-store-type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].use-start-tls=
Whether TLS should be used and enabled when establishing the connection.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].use-start-tls
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.
.properties
files:
1
cas.authn.ldap[0].use-start-tls=...
1
cas:
authn:
ldap[0]:
use-start-tls: "..."
1
java -Dcas.authn.ldap[0].use-start-tls="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_USE_START_TLS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].use-start-tls="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validate-on-checkout=
Whether connections should be validated when loaned out from the pool.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].validate-on-checkout
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.
.properties
files:
1
cas.authn.ldap[0].validate-on-checkout=...
1
cas:
authn:
ldap[0]:
validate-on-checkout: "..."
1
java -Dcas.authn.ldap[0].validate-on-checkout="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATE_ON_CHECKOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validate-on-checkout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validate-period=
Period at which pool should be validated.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].validate-period
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.
.properties
files:
1
cas.authn.ldap[0].validate-period=...
1
cas:
authn:
ldap[0]:
validate-period: "..."
1
java -Dcas.authn.ldap[0].validate-period="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATE_PERIOD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validate-period="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validate-periodically=
Whether connections should be validated periodically when the pool is idle.
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].validate-periodically
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.
.properties
files:
1
cas.authn.ldap[0].validate-periodically=...
1
cas:
authn:
ldap[0]:
validate-periodically: "..."
1
java -Dcas.authn.ldap[0].validate-periodically="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATE_PERIODICALLY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validate-periodically="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validate-timeout=
Period at which validation operations may time out.
This settings supports the
java.time.Duration
syntax [?].
org.apereo.cas.configuration.model.support.ldap.LdapAuthenticationProperties.
CAS Property: cas.authn.ldap[].validate-timeout
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.
.properties
files:
1
cas.authn.ldap[0].validate-timeout=...
1
cas:
authn:
ldap[0]:
validate-timeout: "..."
1
java -Dcas.authn.ldap[0].validate-timeout="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validate-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.attribute-name=objectClass
Attribute name to use for the compare validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].validator.attribute-name=objectClass
1
cas:
authn:
ldap[0]:
validator:
attribute-name: "objectClass"
1
java -Dcas.authn.ldap[0].validator.attribute-name="objectClass" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_ATTRIBUTE_NAME="objectClass"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.attribute-name="objectClass"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.attribute-value=top
Attribute values to use for the compare validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.attribute-value
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.
.properties
files:
1
cas.authn.ldap[0].validator.attribute-value=top
1
cas:
authn:
ldap[0]:
validator:
attribute-value: "top"
1
java -Dcas.authn.ldap[0].validator.attribute-value="top" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_ATTRIBUTE_VALUE="top"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.attribute-value="top"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.base-dn=
Base DN to use for the search request of the search validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.base-dn
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.
.properties
files:
1
cas.authn.ldap[0].validator.base-dn=...
1
cas:
authn:
ldap[0]:
validator:
base-dn: "..."
1
java -Dcas.authn.ldap[0].validator.base-dn="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_BASE_DN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.base-dn="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.dn=
DN to compare to use for the compare validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.dn
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.
.properties
files:
1
cas.authn.ldap[0].validator.dn=...
1
cas:
authn:
ldap[0]:
validator:
dn: "..."
1
java -Dcas.authn.ldap[0].validator.dn="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_DN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.dn="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.scope=OBJECT
Search scope to use for the search request of the search validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.scope
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.
.properties
files:
1
cas.authn.ldap[0].validator.scope=OBJECT
1
cas:
authn:
ldap[0]:
validator:
scope: "OBJECT"
1
java -Dcas.authn.ldap[0].validator.scope="OBJECT" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_SCOPE="OBJECT"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.scope="OBJECT"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.search-filter=(objectClass=*)
Search filter to use for the search request of the search validator.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.search-filter
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.
.properties
files:
1
cas.authn.ldap[0].validator.search-filter=(objectClass=*)
1
cas:
authn:
ldap[0]:
validator:
search-filter: "(objectClass=*)"
1
java -Dcas.authn.ldap[0].validator.search-filter="(objectClass=*)" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_SEARCH_FILTER="(objectClass=*)"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.search-filter="(objectClass=*)"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].validator.type=search
Determine the LDAP validator type.
The following LDAP validators can be used to test connection health status:-
search
: Validates a connection is healthy by performing a search operation. Validation is considered successful if the search result size is greater than zero. -
none
: No validation takes place. -
compare
: Validates a connection is healthy by performing a compare operation.
org.apereo.cas.configuration.model.support.ldap.LdapValidatorProperties.
CAS Property: cas.authn.ldap[].validator.type
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.
.properties
files:
1
cas.authn.ldap[0].validator.type=search
1
cas:
authn:
ldap[0]:
validator:
type: "search"
1
java -Dcas.authn.ldap[0].validator.type="search" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_VALIDATOR_TYPE="search"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].validator.type="search"
cas.war
with an embedded server container and can be found in the build/libs
directory.
Please review this guide to configure your build.
LDAP Scriptable Search Filter
LDAP search filters can point to an external Groovy script to dynamically construct the final filter template.
The script itself may be designed as:
1
2
3
4
5
6
7
8
9
import org.ldaptive.*
import org.springframework.context.*
def run(Object[] args) {
def (filter,parameters,applicationContext,logger) = args
logger.info("Configuring LDAP filter")
filter.setFilter("uid=something")
}
The following parameters are passed to the script:
Parameter | Description |
---|---|
filter |
FilterTemplate to be updated by the script and used for the LDAP query. |
parameters |
Map of query parameters which may be used to construct the final filter. |
applicationContext |
Reference to the Spring ApplicationContext reference. |
logger |
The object responsible for issuing log messages such as logger.info(...) . |
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
cas.authn.ldap[0].password-encoder.encoding-algorithm=
The encoding algorithm to use such as
CAS Property:
|
1 |
cas.authn.ldap[0].password-encoder.encoding-algorithm=... |
1
cas:
authn:
ldap[0]:
password-encoder:
encoding-algorithm: "..."
1
java -Dcas.authn.ldap[0].password-encoder.encoding-algorithm="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_ENCODING_ALGORITHM="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.encoding-algorithm="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.type=NONE
Define the password encoder type to use.
Type may be specified as blank or NONE
to disable password encoding.
It may also refer to a fully-qualified class name that implements
the Spring Security's PasswordEncoder
interface
if you wish you define your own encoder.
-
NONE
: No password encoding (i.e. plain-text) takes place. -
DEFAULT
: Use theDefaultPasswordEncoder
of CAS. For message-digest algorithms viacharacter-encoding
andencoding-algorithm
. -
BCRYPT
: Use theBCryptPasswordEncoder
based on the strength provided and an optional secret. -
SCRYPT
: Use theSCryptPasswordEncoder
. -
PBKDF2
: Use thePbkdf2PasswordEncoder
based on the strength provided and an optional secret. -
STANDARD
: Use theStandardPasswordEncoder
based on the secret provided. -
SSHA
: Use theLdapShaPasswordEncoder
supports Ldap SHA and SSHA (salted-SHA). The values are base-64 encoded and have the label {SHA} or {SSHA} prepended to the encoded hash. -
GLIBC_CRYPT
: Use theGlibcCryptPasswordEncoder
based on theencoding-algorithm
, strength provided and an optional secret. -
org.example.MyEncoder
: An implementation ofPasswordEncoder
of your own choosing. -
file:///path/to/script.groovy
: Path to a Groovy script charged with handling password encoding operations.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.type
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.type=NONE
1
cas:
authn:
ldap[0]:
password-encoder:
type: "NONE"
1
java -Dcas.authn.ldap[0].password-encoder.type="NONE" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_TYPE="NONE"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.type="NONE"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.character-encoding=UTF-8
The encoding algorithm to use such as 'UTF-8'.
Relevant when the type used is DEFAULT
.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.character-encoding
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.character-encoding=UTF-8
1
cas:
authn:
ldap[0]:
password-encoder:
character-encoding: "UTF-8"
1
java -Dcas.authn.ldap[0].password-encoder.character-encoding="UTF-8" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_CHARACTER_ENCODING="UTF-8"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.character-encoding="UTF-8"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.hash-length=16
When used by PasswordEncoderTypes#ARGON2
, it indicates the hash strength/length.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.hash-length
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.hash-length=16
1
cas:
authn:
ldap[0]:
password-encoder:
hash-length: "16"
1
java -Dcas.authn.ldap[0].password-encoder.hash-length="16" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_HASH_LENGTH="16"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.hash-length="16"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.iterations=310000
When used by PasswordEncoderTypes#PBKDF2
, it indicates the required number of iterations.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.iterations
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.iterations=310000
1
cas:
authn:
ldap[0]:
password-encoder:
iterations: "310000"
1
java -Dcas.authn.ldap[0].password-encoder.iterations="310000" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_ITERATIONS="310000"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.iterations="310000"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.secret=
Secret to use with PasswordEncoderTypes#STANDARD
, PasswordEncoderTypes#PBKDF2
,
PasswordEncoderTypes#BCRYPT
, PasswordEncoderTypes#GLIBC_CRYPT
password encoders.
Secret usually is an optional setting.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.secret
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.secret=...
1
cas:
authn:
ldap[0]:
password-encoder:
secret: "..."
1
java -Dcas.authn.ldap[0].password-encoder.secret="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_SECRET="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.secret="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-encoder.strength=16
Strength or number of iterations to use for password hashing.
Usually relevant when dealing with PasswordEncoderTypes#BCRYPT
, PasswordEncoderTypes#PBKDF2
or PasswordEncoderTypes#GLIBC_CRYPT
.
When used by PasswordEncoderTypes#ARGON2
or PasswordEncoderTypes#PBKDF2
, it indicates the salt strength.
org.apereo.cas.configuration.model.core.authentication.PasswordEncoderProperties.
CAS Property: cas.authn.ldap[].password-encoder.strength
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.
.properties
files:
1
cas.authn.ldap[0].password-encoder.strength=16
1
cas:
authn:
ldap[0]:
password-encoder:
strength: "16"
1
java -Dcas.authn.ldap[0].password-encoder.strength="16" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_ENCODER_STRENGTH="16"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-encoder.strength="16"
cas.war
with an embedded server container and can be found in the build/libs
directory.
If you need to design your own password encoding scheme where the type is specified as a fully qualified Java class name, the structure of the class would be similar to the following:
1
2
3
4
5
6
7
8
9
10
11
package org.example.cas;
import org.springframework.security.crypto.codec.*;
import org.springframework.security.crypto.password.*;
public class MyEncoder extends AbstractPasswordEncoder {
@Override
protected byte[] encode(CharSequence rawPassword, byte[] salt) {
return ...
}
}
If you need to design your own password encoding scheme where the type is specified as a path to a Groovy script, the structure of the script would be similar to the following:
1
2
3
4
5
6
7
8
9
10
11
12
import java.util.*
byte[] run(final Object... args) {
def (rawPassword,generatedSalt,logger,applicationContext) = args
logger.debug("Encoding password...")
return ...
}
Boolean matches(final Object... args) {
def (rawPassword,encodedPassword,logger,applicationContext) = args
logger.debug("Does match or not ?");
return ...
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
cas.authn.ldap[0].password-policy.groovy.location=
Handle password policy via Groovy script. 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, specially if the script set to reload on changes, you may need to adjust the total number ofinotify 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 .
CAS Property:
|
1 |
cas.authn.ldap[0].password-policy.groovy.location=... |
1
cas:
authn:
ldap[0]:
password-policy:
groovy:
location: "..."
1
java -Dcas.authn.ldap[0].password-policy.groovy.location="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_GROOVY_LOCATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.groovy.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.account-state-handling-enabled=true
Indicates whether account state handling should be enabled to process warnings or errors reported back from the authentication response, produced by the source.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.account-state-handling-enabled
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.account-state-handling-enabled=true
1
cas:
authn:
ldap[0]:
password-policy:
account-state-handling-enabled: "true"
1
java -Dcas.authn.ldap[0].password-policy.account-state-handling-enabled="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_ACCOUNT_STATE_HANDLING_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.account-state-handling-enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.custom-policy-class=
An implementation of a policy class that knows how to handle LDAP responses.
The class must be an implementation of org.ldaptive.auth.AuthenticationResponseHandler
.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.custom-policy-class
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.custom-policy-class=...
1
cas:
authn:
ldap[0]:
password-policy:
custom-policy-class: "..."
1
java -Dcas.authn.ldap[0].password-policy.custom-policy-class="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_CUSTOM_POLICY_CLASS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.custom-policy-class="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.display-warning-on-match=true
Indicates if warning should be displayed, when the ldap attribute value
matches the #warningAttributeValue
.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.display-warning-on-match
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.display-warning-on-match=true
1
cas:
authn:
ldap[0]:
password-policy:
display-warning-on-match: "true"
1
java -Dcas.authn.ldap[0].password-policy.display-warning-on-match="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_DISPLAY_WARNING_ON_MATCH="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.display-warning-on-match="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.enabled=true
Whether password policy should be enabled.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.enabled
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.enabled=true
1
cas:
authn:
ldap[0]:
password-policy:
enabled: "true"
1
java -Dcas.authn.ldap[0].password-policy.enabled="true" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.login-failures=5
When dealing with FreeIPA, indicates the number of allows login failures.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.login-failures
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.login-failures=5
1
cas:
authn:
ldap[0]:
password-policy:
login-failures: "5"
1
java -Dcas.authn.ldap[0].password-policy.login-failures="5" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_LOGIN_FAILURES="5"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.login-failures="5"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.password-expiration-number-of-days=180
This is used to calculate an expiration period for the account password.
When defined, LDAP password policy handling will use the pwdLastSet
attribute
which must be returned from the LDAP authentication attempt.
LDAP password policy handling will emit a warning for the pwdLastSet
value plus the expiration amount.
A negative value will disable the operations that calculate the expiration period.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.password-expiration-number-of-days
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.password-expiration-number-of-days=180
1
cas:
authn:
ldap[0]:
password-policy:
password-expiration-number-of-days: "180"
1
java -Dcas.authn.ldap[0].password-policy.password-expiration-number-of-days="180" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_PASSWORD_EXPIRATION_NUMBER_OF_DAYS="180"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.password-expiration-number-of-days="180"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.policy-attributes=
Key-value structure (Map) that indicates a list of boolean attributes as keys.
If either attribute value is true, indicating an account state is flagged,
the corresponding error can be thrown.
Example accountLocked=javax.security.auth.login.AccountLockedException
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.policy-attributes
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.policy-attributes=...
1
cas:
authn:
ldap[0]:
password-policy:
policy-attributes: "..."
1
java -Dcas.authn.ldap[0].password-policy.policy-attributes="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_POLICY_ATTRIBUTES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.policy-attributes="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.strategy=DEFAULT
Decide how authentication should handle password policy changes. Available values are as follows:
-
DEFAULT
: Default option to handle policy changes. -
GROOVY
: Handle account password policies via Groovy. -
REJECT_RESULT_CODE
: Strategy to only activate password policy if the authentication response code is not blocked.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.strategy
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.strategy=DEFAULT
1
cas:
authn:
ldap[0]:
password-policy:
strategy: "DEFAULT"
1
java -Dcas.authn.ldap[0].password-policy.strategy="DEFAULT" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_STRATEGY="DEFAULT"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.strategy="DEFAULT"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.type=GENERIC
LDAP type.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.type
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.type=GENERIC
1
cas:
authn:
ldap[0]:
password-policy:
type: "GENERIC"
1
java -Dcas.authn.ldap[0].password-policy.type="GENERIC" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_TYPE="GENERIC"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.type="GENERIC"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warn-all=
Always display the password expiration warning regardless.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warn-all
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warn-all=...
1
cas:
authn:
ldap[0]:
password-policy:
warn-all: "..."
1
java -Dcas.authn.ldap[0].password-policy.warn-all="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARN_ALL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warn-all="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-attribute-name=
Used by an account state handling policy that only calculates account warnings in case the entry carries this attribute.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-attribute-name
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-attribute-name=...
1
cas:
authn:
ldap[0]:
password-policy:
warning-attribute-name: "..."
1
java -Dcas.authn.ldap[0].password-policy.warning-attribute-name="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_ATTRIBUTE_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-attribute-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-attribute-value=
Used by an account state handling policy that only calculates account warnings
in case the entry carries an attribute #warningAttributeName
whose value matches this field.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-attribute-value
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-attribute-value=...
1
cas:
authn:
ldap[0]:
password-policy:
warning-attribute-value: "..."
1
java -Dcas.authn.ldap[0].password-policy.warning-attribute-value="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_ATTRIBUTE_VALUE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-attribute-value="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].password-policy.warning-days=30
This is used to calculate a warning period to see if account expiry is within the calculated window.
org.apereo.cas.configuration.model.support.ldap.LdapPasswordPolicyProperties.
CAS Property: cas.authn.ldap[].password-policy.warning-days
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.
.properties
files:
1
cas.authn.ldap[0].password-policy.warning-days=30
1
cas:
authn:
ldap[0]:
password-policy:
warning-days: "30"
1
java -Dcas.authn.ldap[0].password-policy.warning-days="30" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PASSWORD_POLICY_WARNING_DAYS="30"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].password-policy.warning-days="30"
cas.war
with an embedded server container and can be found in the build/libs
directory.
Password Policy Strategies
If the password policy strategy is to be handed off to a Groovy script, the outline of the script may be as follows:
1
2
3
4
5
6
7
8
9
10
11
12
13
import java.util.*
import org.ldaptive.auth.*
import org.apereo.cas.*
import org.apereo.cas.authentication.*
import org.apereo.cas.authentication.support.*
List<MessageDescriptor> run(final Object... args) {
def (response,configuration,logger,applicationContext) = args
logger.info("Handling password policy [{}] via ${configuration.getAccountStateHandler()}", response)
def accountStateHandler = configuration.getAccountStateHandler()
return accountStateHandler.handle(response, configuration)
}
The parameters passed are as follows:
Parameter | Description |
---|---|
response |
The LDAP authentication response of type org.ldaptive.auth.AuthenticationResponse
|
configuration |
The LDAP password policy configuration carrying the account state handler defined. |
logger |
The object responsible for issuing log messages such as logger.info(...) . |
applicationContext |
The Spring ApplicationContext that allows one to interact with the runtime. |
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
cas.authn.ldap[0].principal-transformation.groovy.location=
Transform usernames using a Groovy resource. 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, specially if the script set to reload on changes, you may need to adjust the total number ofinotify 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 .
CAS Property:
|
1 |
cas.authn.ldap[0].principal-transformation.groovy.location=... |
1
cas:
authn:
ldap[0]:
principal-transformation:
groovy:
location: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.groovy.location="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_GROOVY_LOCATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.groovy.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.blocking-pattern=
A regular expression that will be used against the username to match for blocking/forbidden values. If a match is found, an exception will be thrown and principal transformation will fail.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.blocking-pattern
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.blocking-pattern=...
1
cas:
authn:
ldap[0]:
principal-transformation:
blocking-pattern: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.blocking-pattern="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_BLOCKING_PATTERN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.blocking-pattern="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.case-conversion=NONE
Indicate whether the principal identifier should be transformed into upper-case, lower-case, etc. Available values are as follows:
-
NONE
: No conversion. -
LOWERCASE
: Lowercase conversion. -
UPPERCASE
: Uppercase conversion.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.case-conversion
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.case-conversion=NONE
1
cas:
authn:
ldap[0]:
principal-transformation:
case-conversion: "NONE"
1
java -Dcas.authn.ldap[0].principal-transformation.case-conversion="NONE" -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_CASE_CONVERSION="NONE"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.case-conversion="NONE"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.pattern=
A regular expression that will be used against the provided username for username extractions. On a successful match, the first matched group in the pattern will be used as the extracted username.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.pattern
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.pattern=...
1
cas:
authn:
ldap[0]:
principal-transformation:
pattern: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.pattern="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_PATTERN="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.pattern="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.prefix=
Prefix to add to the principal id prior to authentication.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.prefix
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.prefix=...
1
cas:
authn:
ldap[0]:
principal-transformation:
prefix: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.prefix="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_PREFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.ldap[0].principal-transformation.suffix=
Suffix to add to the principal id prior to authentication.
This setting supports the Spring Expression Language.
org.apereo.cas.configuration.model.core.authentication.PrincipalTransformationProperties.
CAS Property: cas.authn.ldap[].principal-transformation.suffix
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.
.properties
files:
1
cas.authn.ldap[0].principal-transformation.suffix=...
1
cas:
authn:
ldap[0]:
principal-transformation:
suffix: "..."
1
java -Dcas.authn.ldap[0].principal-transformation.suffix="..." -jar build/libs/cas.war
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.
1
2
3
export CAS_AUTHN_LDAP[0]_PRINCIPAL_TRANSFORMATION_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --cas.authn.ldap[0].principal-transformation.suffix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
Authentication handlers that generally deal with username-password credentials can be configured to transform the user id prior to executing the authentication sequence. Each authentication strategy in CAS provides settings to properly transform the principal. Refer to the relevant settings for the authentication strategy at hand to learn more.
Authentication handlers as part of principal transformation may also be provided a path to a Groovy script to transform the provided username. The outline of the script may take on the following form:
1
2
3
4
String run(final Object... args) {
def (providedUsername,logger) = args
return providedUsername.concat("SomethingElse")
}
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
Certain authentication handlers are allowed to determine whether they can operate on the provided credential and as such lend themselves to be tried and tested during the authentication handler selection phase. The credential criteria may be one of the following options:
- A regular expression pattern that is tested against the credential identifier.
- A fully qualified class name of your own design that looks similar to the below example:
1
2
3
4
5
6
7
8
9
import java.util.function.Predicate;
import org.apereo.cas.authentication.Credential;
public class PredicateExample implements Predicate<Credential> {
@Override
public boolean test(final Credential credential) {
// Examine the credential and return true/false
}
}
- Path to an external Groovy script that looks similar to the below example:
1
2
3
4
5
6
7
8
9
import org.apereo.cas.authentication.Credential
import java.util.function.Predicate
class PredicateExample implements Predicate<Credential> {
@Override
boolean test(final Credential credential) {
// test and return result
}
}
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
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.
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.
Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas
. All other settings are controlled and provided
to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with
the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition
or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the
way you intend.
Validation
Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value
. The index [0]
is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
Password Policy Enforcement
To learn how to enforce a password policy for LDAP, please review this guide.
Password Policy Enforcement
You may also be interested in synchronizing account passwords with one or more LDAP servers. To learn more, please review this guide.
Troubleshooting
To enable additional logging, modify the logging configuration file to add the following:
1
2
3
4
<Logger name="org.ldaptive" level="debug" additivity="false">
<AppenderRef ref="casConsole"/>
<AppenderRef ref="casFile"/>
</Logger>