SPNEGO Authentication
SPNEGO is an authentication technology that is primarily used to provide transparent CAS authentication to browsers running on Windows running under Active Directory domain credentials. There are three actors involved: the client, the CAS server, and the Active Directory Domain Controller/KDC.
- Client sends CAS: HTTP
GETto CAS for cas protected page - CAS responds: HTTP
401- Access DeniedWWW-Authenticate: Negotiate - Client sends ticket request: Kerberos(
KRB_TGS_REQ) Requesting ticket forHTTP/cas.example.com@REALM - Kerberos KDC responds: Kerberos(
KRB_TGS_REP) Granting ticket forHTTP/cas.example.com@REALM - Client sends CAS: HTTP
GETAuthorization: Negotiate w/SPNEGO Token - CAS responds: HTTP
200- OKWWW-Authenticatew/SPNEGO response + requested page.
The above interaction occurs only for the first request, when there is no CAS SSO session. Once CAS grants a ticket-granting ticket, the SPNEGO process will not happen again until the CAS ticket expires.
Requirements
- Client is logged in to a Windows Active Directory domain.
- Supported browser.
- CAS is running MIT kerberos against the AD domain controller.
It's safe to make
sure you have the proper JCE bundle installed in your Java environment that is used
by CAS, specially if you need to consume encrypted payloads issued by ADFS. Be sure
to pick the right version of the JCE for your Java version. Java versions can be
detected via the java -version command.
If organization
users have large kerberos tickets, likely cause by being a member of a large number
of groups, the Tomcat connector will need to have the maxHttpHeaderSize
value increased from the default amount to allow the ticket to be passed to the CAS Server application.
Components
SPNEGO support is enabled by including the following dependency in the WAR overlay:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-spnego-webflow</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-spnego-webflow:${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-spnego-webflow"
}
1
2
3
4
5
6
7
8
9
10
dependencies {
/*
The following platform references are included automatically and are listed 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-spnego-webflow"
}
JCIFS SDK
Note that jcifs-ext library is no longer published to a public Maven repository. This means that you will need to download
the necessary JAR files and include them in your build configuration. The SDK may be downloaded
from the CAS codebase. Then,
assuming the SDK is placed inside a lib directory of the WAR overlay
directory, it can be referenced in the build configuration as such:
1
implementation files("${projectDir}/lib/jcifs-ext.jar")
Configuration
The following steps are required to turn on the SPNEGO functionality.
Create SPN Account
Create an Active Directory account for the Service Principal Name (SPN) and record the username. Password will be overwritten by the next step.
Create Keytab File
The keytab file enables a trust link between the CAS server and the Key Distribution Center (KDC); an Active Directory
domain controller serves the role of KDC in this context.
The ktpass tool is used to generate the keytab file,
which contains a cryptographic key. Be sure to execute the command from an Active Directory domain controller as
administrator (a member of domain administrators will not be able to use ktpass successfully).
Example:
1
2
3
4
5
6
7
8
9
10
11
C:\Users\administrator.DOMAIN>ktpass /out myspnaccount.keytab /princ HTTP/cas.example.com@REALM /pass * /mapuser domain-account@YOUR.REALM /ptype KRB5_NT_PRINCIPAL /crypto AES256-SHA1
Targeting domain controller: DC.YOUR.REALM
Successfully mapped HTTP/cas.example.com to domain-account.
Type the password for HTTP/cas.example.com:
Type the password again to confirm:
Password successfully set!
Key created.
Output keytab to myspnaccount.keytab:
Keytab version: 0x502
keysize 93 HTTP/cas.example.com@REALM ptype 1 (KRB5_NT_PRINCIPAL) vno 5 etype 0x12 (AES256-SHA1) keylength 32
(0x00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff)
Using ktpass requires Active Directory admin permissions. If that is not an option, you may be able to use ktab.exe from %JAVA_HOME%\bin\ktab.exe that
is provided by the JDK:
1
%JAVA_HOME%\bin\ktab.exe -a service_xxx -n 0 -k cas.keytab
-k specifies key tab output file name and -n 0 specifies the KNVO number if available and found for the user account. This value may match the msDS-KeyVersionNumber on the user account.
Also note that the keytab file must be regenerated after password changes, if any.
Test SPN Account
Install and configure MIT Kerberos V on the CAS server host(s). The following sample krb5.conf file may be used
as a reference.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
ticket_lifetime = 24000
default_realm = YOUR.REALM.HERE
default_keytab_name = /home/cas/kerberos/myspnaccount.keytab
dns_lookup_realm = false
dns_lookup_kdc = false
default_tkt_enctypes = rc4-hmac
default_tgs_enctypes = rc4-hmac
[realms]
YOUR.REALM.HERE = {
kdc = your.kdc.your.realm.here:88
}
[domain_realm]
.your.realm.here = YOUR.REALM.HERE
your.realm.here = YOUR.REALM.HERE
It is important to note that myspnaccount.keytab is declared as default keytab, otherwise CAS may not be able to
find it and will raise an exception similar to
1
KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP -RC4 with HMAC`
Then verify that your are able to read the keytab file:
1
2
3
4
5
klist -k
Keytab name: FILE:/home/cas/kerberos/myspnaccount.keytab
KVNO Principal
---- --------------------------------------------------------------------------
3 HTTP/cas.example.com@REALM
Then verify that your are able to use the keytab file:
1
2
3
4
5
6
7
8
kinit -k HTTP/cas.example.com@REALM
klist
Ticket cache: FILE:/tmp/krb5cc_999
Default principal: HTTP/cas.example.com@REALM
Valid starting Expires Service principal
12/08/2016 10:52:00 12/08/2016 20:52:00 krbtgt/REALM@REALM
renew until 12/08/2016 20:52:00
Browser Configuration
- Internet Explorer - Enable
Integrated Windows Authenticationand add the CAS server URL to theLocal Intranetzone. - Firefox - Set the
network.negotiate-auth.trusted-urisconfiguration parameter inabout:configto the CAS server URL, e.g.https://cas.example.com.
Authentication Configuration
Make sure you have at least specified the JCIFS Service Principal in the CAS configuration.
The following settings and properties are available from the CAS configuration catalog:
cas.authn.spnego.ldap.base-dnBase DN to use.
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.
cas.authn.spnego.ldap.bind-credentialThe bind credential to use when connecting to LDAP.
The bind credential to use when connecting to LDAP.
cas.authn.spnego.ldap.bind-dnThe bind DN to use when connecting to LDAP.
-
bindDn/bindCredentialprovided - Use the provided credentials to bind when initializing connections. -
bindDn/bindCredentialset to*- Use a fast-bind strategy to initialize the pool. -
bindDn/bindCredentialset to blank - Skip connection initializing; perform operations anonymously. - SASL mechanism provided - Use the given SASL mechanism to bind when initializing connections.
cas.authn.spnego.ldap.ldap-urlThe LDAP url to the server.
The LDAP url to the server. More than one may be specified, separated by space and/or comma.
cas.authn.spnego.ldap.search-filterUser filter to use for searching.
User filter to use for searching. Syntax is cn={user} or cn={0}.
You may also provide an external groovy script in the syntax of file:/path/to/GroovyScript.groovy to fully build the final filter template dynamically.
cas.authn.spnego.principal-transformation.groovy.locationThe location of the 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, especially if the script is set to reload on changes, you may need to adjust the total number of inotify instances. On Linux, you may need to add the following line to /etc/sysctl.conf: fs.inotify.max_user_instances = 256.
You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.
In situations and scenarios where CAS is able to automatically watch the underlying resource for changes and detect updates and modifications dynamically, you may be able to specify the following setting as either an environment variable or system property with a value of false to disable the resource watcher: org.apereo.cas.util.io.PathWatcherService.
cas.authn.spnego.principal.principal-transformation.groovy.locationThe location of the 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, especially if the script is set to reload on changes, you may need to adjust the total number of inotify instances. On Linux, you may need to add the following line to /etc/sysctl.conf: fs.inotify.max_user_instances = 256.
You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.
In situations and scenarios where CAS is able to automatically watch the underlying resource for changes and detect updates and modifications dynamically, you may be able to specify the following setting as either an environment variable or system property with a value of false to disable the resource watcher: org.apereo.cas.util.io.PathWatcherService.
cas.authn.spnego.properties[0].jcifs-service-principalThe Jcifs service principal.
HTTP/cas.example.com@EXAMPLE.COMThe Jcifs service principal.
cas.authn.spnego.alternative-remote-host-attributeAlternative header name to use in order to find the host address.
alternateRemoteHeaderAlternative header name to use in order to find the host address.
cas.authn.spnego.dns-timeoutWhen validating clients, specifies the DNS timeout used to look up an address.
PT2SWhen validating clients, specifies the DNS timeout used to look up an address.
cas.authn.spnego.host-name-client-action-strategyThe bean id of a webflow action whose job is to evaluate the client host to see if the request is authorized for spnego.
hostnameSpnegoClientActionThe bean id of a webflow action whose job is to evaluate the client host to see if the request is authorized for spnego. Supported strategies include hostnameSpnegoClientAction where CAS checks to see if the request’s remote hostname matches a predefine pattern. and ldapSpnegoClientAction where CAS checks an LDAP instance for the remote hostname, to locate a pre-defined attribute whose mere existence would allow the webflow to resume to SPNEGO.
cas.authn.spnego.host-name-pattern-stringA regex pattern that indicates whether the client host name is allowed for spnego.
.+A regex pattern that indicates whether the client host name is allowed for spnego.
cas.authn.spnego.ips-to-check-patternA regex pattern that indicates whether the client IP is allowed for spnego.
127.+A regex pattern that indicates whether the client IP is allowed for spnego.
cas.authn.spnego.ldap.allow-multiple-dnsWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
falseWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
cas.authn.spnego.ldap.allow-multiple-entriesSet if multiple Entries are allowed.
falseSet if multiple Entries are allowed.
cas.authn.spnego.ldap.binary-attributesIndicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
Indicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
cas.authn.spnego.ldap.block-wait-timeThe length of time the pool will block.
PT3SThe 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
cas.authn.spnego.ldap.connect-timeoutSets the maximum amount of time that connects will block.
PT5SSets the maximum amount of time that connects will block.
cas.authn.spnego.ldap.connection-strategyIf multiple URLs are provided as the ldapURL this describes how each URL will be processed.
-
ACTIVE_PASSIVEFirst LDAP will be used for every request unless it fails and then the next shall be used. -
ROUND_ROBINFor each new connection the next url in the list will be used. -
RANDOMFor each new connection a random LDAP url will be selected. -
DNS_SRVLDAP urls based on DNS SRV records of the configured/given LDAP url will be used.
cas.authn.spnego.ldap.disable-poolingWhether to use a pooled connection factory in components.
falseWhether to use a pooled connection factory in components.
cas.authn.spnego.ldap.fail-fastAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
trueAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
cas.authn.spnego.ldap.follow-referralsSet if search referrals should be followed.
trueSet if search referrals should be followed.
cas.authn.spnego.ldap.hostname-verifierHostname verification options.
DEFAULT-
DEFAULT: Default option, forcing verification. -
ANY: Skip hostname verification and allow all.
cas.authn.spnego.ldap.idle-timeRemoves connections from the pool based on how long they have been idle in the available queue.
PT10MRemoves 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.
cas.authn.spnego.ldap.keystorePath to the keystore used for SSL connections.
Path to the keystore used for SSL connections. Typically contains SSL certificates for the LDAP server.
cas.authn.spnego.ldap.keystore-passwordKeystore password.
Keystore password.
cas.authn.spnego.ldap.keystore-typeThe type of keystore.
The type of keystore. PKCS12 or JKS. If left blank, defaults to the default keystore type indicated by the underlying Java platform.
cas.authn.spnego.ldap.max-pool-sizeMaximum LDAP connection pool size which the pool can use to grow.
10Maximum LDAP connection pool size which the pool can use to grow.
cas.authn.spnego.ldap.min-pool-sizeMinimum LDAP connection pool size.
3Minimum LDAP connection pool size. Size the pool should be initialized to and pruned to
cas.authn.spnego.ldap.nameName of the LDAP handler.
Name of the LDAP handler.
cas.authn.spnego.ldap.page-sizeRequest that the server return results in batches of a specific size.
0Request 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.
cas.authn.spnego.ldap.pool-passivatorYou 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.
BINDDIRECT 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.
cas.authn.spnego.ldap.prune-periodRemoves connections from the pool based on how long they have been idle in the available queue.
PT2HRemoves connections from the pool based on how long they have been idle in the available queue. Run the pruning process at the indicated interval.
cas.authn.spnego.ldap.response-timeoutDuration of time to wait for responses.
PT5SDuration of time to wait for responses.
cas.authn.spnego.ldap.sasl-authorization-idSASL authorization id.
SASL authorization id.
cas.authn.spnego.ldap.sasl-mechanismThe SASL mechanism.
The SASL mechanism.
cas.authn.spnego.ldap.sasl-mutual-authWhether SASL mutual authentication is enabled.
Whether SASL mutual authentication is enabled.
cas.authn.spnego.ldap.sasl-quality-of-protectionSASL quality of protected.
SASL quality of protected.
cas.authn.spnego.ldap.sasl-realmThe SASL realm.
The SASL realm.
cas.authn.spnego.ldap.sasl-security-strengthSASL security strength.
SASL security strength.
cas.authn.spnego.ldap.search-entry-handlersSearch handlers.
Search handlers.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-name-case-changeThe Attribute name case change.
The Attribute name case change.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-namesThe Attribute names.
The Attribute names.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-value-case-changeThe Attribute value case change.
The Attribute value case change.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.dn-case-changeThe Dn case change.
The Dn case change.
cas.authn.spnego.ldap.search-entry-handlers[0].dn-attribute.add-if-existsThe Add if exists.
The Add if exists.
cas.authn.spnego.ldap.search-entry-handlers[0].dn-attribute.dn-attribute-nameThe Dn attribute name.
entryDNThe Dn attribute name.
cas.authn.spnego.ldap.search-entry-handlers[0].merge-attribute.attribute-namesThe Attribute names.
The Attribute names.
cas.authn.spnego.ldap.search-entry-handlers[0].merge-attribute.merge-attribute-nameThe Merge attribute name.
The Merge attribute name.
cas.authn.spnego.ldap.search-entry-handlers[0].primary-group-id.base-dnThe Base dn.
The Base dn.
cas.authn.spnego.ldap.search-entry-handlers[0].primary-group-id.group-filterThe Group filter.
(&(objectClass=group)(objectSid={0}))The Group filter.
cas.authn.spnego.ldap.search-entry-handlers[0].recursive.merge-attributesThe Merge attributes.
The Merge attributes.
cas.authn.spnego.ldap.search-entry-handlers[0].recursive.search-attributeThe Search attribute.
The Search attribute.
cas.authn.spnego.ldap.search-entry-handlers[0].search-referral.limitThe default referral limit.
10The default referral limit.
cas.authn.spnego.ldap.search-entry-handlers[0].search-result.limitThe default referral limit.
10The default referral limit.
cas.authn.spnego.ldap.search-entry-handlers[0].typeThe type of search entry handler to choose.
-
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 theobjectGUIDattribute fetching and conversion. -
OBJECT_SID: Object sid search entry handler. Handles theobjectSidattribute 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 thememberOfattribute 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.
cas.authn.spnego.ldap.subtree-searchWhether subtree searching is allowed.
trueWhether subtree searching is allowed.
cas.authn.spnego.ldap.trust-certificatesPath of the trust certificates to use for the SSL connection.
Path of the trust certificates to use for the SSL connection. Ignores keystore-related settings when activated and used.
cas.authn.spnego.ldap.trust-managerTrust Manager options.
-
DEFAULT: Enable and force the default JVM trust managers. -
ANY: Trust any client or server.
cas.authn.spnego.ldap.trust-storePath to the keystore used to determine which certificates or certificate authorities should be trusted.
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.
cas.authn.spnego.ldap.trust-store-passwordPassword needed to open the truststore.
Password needed to open the truststore.
cas.authn.spnego.ldap.trust-store-typeThe type of trust keystore that determines which certificates or certificate authorities are trusted.
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.
cas.authn.spnego.ldap.use-start-tlsWhether TLS should be used and enabled when establishing the connection.
falseWhether TLS should be used and enabled when establishing the connection.
cas.authn.spnego.ldap.validate-on-checkoutWhether connections should be validated when loaned out from the pool.
trueWhether connections should be validated when loaned out from the pool.
cas.authn.spnego.ldap.validate-periodPeriod at which pool should be validated.
PT5MPeriod at which pool should be validated.
cas.authn.spnego.ldap.validate-periodicallyWhether connections should be validated periodically when the pool is idle.
trueWhether connections should be validated periodically when the pool is idle.
cas.authn.spnego.ldap.validate-timeoutPeriod at which validation operations may time out.
PT5SPeriod at which validation operations may time out.
cas.authn.spnego.ldap.validator.attribute-nameAttribute name to use for the compare validator.
objectClassAttribute name to use for the compare validator.
cas.authn.spnego.ldap.validator.attribute-valueAttribute values to use for the compare validator.
topAttribute values to use for the compare validator.
cas.authn.spnego.ldap.validator.base-dnBase DN to use for the search request of the search validator.
Base DN to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.dnDN to compare to use for the compare validator.
DN to compare to use for the compare validator.
cas.authn.spnego.ldap.validator.scopeSearch scope to use for the search request of the search validator.
OBJECTSearch scope to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.search-filterSearch filter to use for the search request of the search validator.
(objectClass=*)Search filter to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.typeDetermine the LDAP validator type.
searchDetermine the LDAP validator type.
-
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.
cas.authn.spnego.mixed-mode-authenticationIf true, does not terminate authentication and allows CAS to resume and fallback to normal authentication means such as uid/psw via the login page.
falseIf true, does not terminate authentication and allows CAS to resume and fallback to normal authentication means such as uid/psw via the login page. If disallowed, considers spnego authentication to be final in the event of failures.
cas.authn.spnego.nameName of the authentication handler.
Name of the authentication handler.
cas.authn.spnego.ntlm-allowedAllows authentication if spnego credential is marked as NTLM.
trueAllows authentication if spnego credential is marked as NTLM.
cas.authn.spnego.orderThe order of the authentication handler in the chain.
The order of the authentication handler in the chain.
cas.authn.spnego.pool-sizeThe size of the pool used to validate SPNEGO tokens.
10The size of the pool used to validate SPNEGO tokens. A pool is used to provider better performance than what was previously offered by the simple Lombok Synchronized annotation.
cas.authn.spnego.pool-timeoutThe timeout of the pool used to validate SPNEGO tokens.
PT2SThe timeout of the pool used to validate SPNEGO tokens.
cas.authn.spnego.principal-transformation.blocking-patternA regular expression that will be used against the username to match for blocking/forbidden values.
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.
cas.authn.spnego.principal-transformation.case-conversionIndicate whether the principal identifier should be transformed into upper-case, lower-case, etc.
NONE-
NONE: No conversion. -
LOWERCASE: Lowercase conversion. -
UPPERCASE: Uppercase conversion.
cas.authn.spnego.principal-transformation.patternA regular expression that will be used against the provided username for username extractions.
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.
cas.authn.spnego.principal-transformation.prefixPrefix to add to the principal id prior to authentication.
Prefix to add to the principal id prior to authentication.
cas.authn.spnego.principal-transformation.suffixSuffix to add to the principal id prior to authentication.
Suffix to add to the principal id prior to authentication.
cas.authn.spnego.principal-with-domain-nameIf specified, will create the principal by this name on successful authentication.
falseIf specified, will create the principal by this name on successful authentication.
cas.authn.spnego.principal.active-attribute-repository-idsActivated attribute repository identifiers that should be used for fetching attributes if attribute resolution is enabled.
*Activated attribute repository identifiers that should be used for fetching attributes if attribute resolution is enabled. The list here may include identifiers separated by comma.
cas.authn.spnego.principal.attribute-repository-selectionControl the behavior of the attribute repository selection by authentication method or handler.
Control the behavior of the attribute repository selection by authentication method or handler. The map here is keyed by the authentication handler name, and the value is the attribute repository identifiers separated by comma. When the authentication handler is executed, the attribute repositories assigned to this handler will be selected to fetch attributes. Note that the resolution engine will always favor attribute repositories assigned to the service definition, if any and as part of its authentication policy, over this global setting.
cas.authn.spnego.principal.attribute-resolution-enabledWhether attribute repositories should be contacted to fetch person attributes.
undefined-
TRUE: Constant to represent the true state. -
FALSE: Constant to represent the false state. -
UNDEFINED: Constant to represent the undefined state.
cas.authn.spnego.principal.principal-attributeAttribute name to use to indicate the identifier of the principal constructed.
Attribute name to use to indicate the identifier of the principal constructed. If the attribute is blank or has no values, the default principal id will be used determined by the underlying authentication engine. The principal id attribute usually is removed from the collection of attributes collected, though this behavior depends on the schematics of the underlying authentication strategy.
cas.authn.spnego.principal.principal-resolution-conflict-strategyIn the event that the principal resolution engine resolves more than one principal, (especially if such principals in the chain have different identifiers), this setting determines strategy by which the principal id w...
lastIn the event that the principal resolution engine resolves more than one principal, (especially if such principals in the chain have different identifiers), this setting determines strategy by which the principal id would be chosen from the chain. Accepted values are: last, first.
cas.authn.spnego.principal.principal-resolution-failure-fatalWhen true, throws an error back indicating that principal resolution has failed and no principal can be found based on the authentication requirements.
undefined-
TRUE: Constant to represent the true state. -
FALSE: Constant to represent the false state. -
UNDEFINED: Constant to represent the undefined state.
cas.authn.spnego.principal.principal-transformation.blocking-patternA regular expression that will be used against the username to match for blocking/forbidden values.
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.
cas.authn.spnego.principal.principal-transformation.case-conversionIndicate whether the principal identifier should be transformed into upper-case, lower-case, etc.
NONE-
NONE: No conversion. -
LOWERCASE: Lowercase conversion. -
UPPERCASE: Uppercase conversion.
cas.authn.spnego.principal.principal-transformation.patternA regular expression that will be used against the provided username for username extractions.
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.
cas.authn.spnego.principal.principal-transformation.prefixPrefix to add to the principal id prior to authentication.
Prefix to add to the principal id prior to authentication.
cas.authn.spnego.principal.principal-transformation.suffixSuffix to add to the principal id prior to authentication.
Suffix to add to the principal id prior to authentication.
cas.authn.spnego.principal.return-nullReturn a null principal object if no attributes can be found for the principal.
undefined-
TRUE: Constant to represent the true state. -
FALSE: Constant to represent the false state. -
UNDEFINED: Constant to represent the undefined state.
cas.authn.spnego.principal.use-existing-principal-idUses an existing principal id that may have already been established in order to run person directory queries.
undefined-
TRUE: Constant to represent the true state. -
FALSE: Constant to represent the false state. -
UNDEFINED: Constant to represent the undefined state.
cas.authn.spnego.propertiesIndividual authentication settings for spengo that are grouped and fed to the spnego authentication object to form a collection.
Individual authentication settings for spengo that are grouped and fed to the spnego authentication object to form a collection.
cas.authn.spnego.properties[0].cache-policyJcifs Netbios cache policy.
600Jcifs Netbios cache policy.
cas.authn.spnego.properties[0].jcifs-domainThe Jcifs domain.
The Jcifs domain.
cas.authn.spnego.properties[0].jcifs-domain-controllerThe Jcifs domain controller.
The Jcifs domain controller.
cas.authn.spnego.properties[0].jcifs-netbios-winsThe Jcifs netbios wins.
The Jcifs netbios wins.
cas.authn.spnego.properties[0].jcifs-passwordThe Jcifs password.
The Jcifs password.
cas.authn.spnego.properties[0].jcifs-service-passwordThe Jcifs service password.
The Jcifs service password.
cas.authn.spnego.properties[0].jcifs-usernameThe Jcifs username.
The Jcifs username.
cas.authn.spnego.properties[0].timeoutSpnego JCIFS timeout.
PT5MSpnego JCIFS timeout.
cas.authn.spnego.send401-on-authentication-failureIf the authenticated principal cannot be determined from the spegno credential, will set the http status code to 401.
trueIf the authenticated principal cannot be determined from the spegno credential, will set the http status code to 401.
cas.authn.spnego.spnego-attribute-nameIn case LDAP is used to validate clients, this is the attribute that indicates the host.
distinguishedNameIn case LDAP is used to validate clients, this is the attribute that indicates the host.
cas.authn.spnego.supported-browsersBegins negotiating spnego if the user-agent is one of the supported browsers.
MSIE,Trident,Firefox,AppleWebKitBegins negotiating spnego if the user-agent is one of the supported browsers.
cas.authn.spnego.system.kerberos-confThe Kerberos conf.
The Kerberos conf. As with all Kerberos installations, a Kerberos Key Distribution Center (KDC) is required. It needs to contain the user name and password you will use to be authenticated to Kerberos. As with most Kerberos installations, a Kerberos configuration file krb5.conf is consulted to determine such things as the default realm and KDC. Typically, the default realm and the KDC for that realm are indicated in the Kerberos krb5.conf configuration file. The path to the configuration file must typically be defined as an absolute path.
cas.authn.spnego.system.kerberos-debugThe Kerberos debug.
The Kerberos debug.
cas.authn.spnego.system.kerberos-kdcThe Kerberos kdc.
172.10.1.10The Kerberos kdc.
cas.authn.spnego.system.kerberos-realmThe Kerberos realm.
EXAMPLE.COMThe Kerberos realm.
cas.authn.spnego.system.login-confThe Login conf.Absolute path to the jaas login configuration file.
The Login conf.Absolute path to the jaas login configuration file. This should define the spnego authentication details. Make sure you have at least specified the JCIFS Service Principal defined.
cas.authn.spnego.system.use-subject-creds-onlyThe Use subject creds only.
falseThe Use subject creds only.
cas.authn.spnego.webflow.enabledWhether webflow auto-configuration should be enabled.
trueWhether webflow auto-configuration should be enabled.
cas.authn.spnego.webflow.orderThe order in which the webflow is configured.
0The order in which the webflow is configured.
Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.
Groovy scripting
CAS takes advantage of Apache Groovy in forms of either embedded or external scripts that allow one to, by default, dynamically build constructs, attributes, access strategies and a lot more. To activate the functionality described here, you may need to prepare CAS to support and integrate with Apache Groovy.
Please review this guide to configure your build.
LDAP & Active Directory
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.
Principal transformation
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.
Notes on configuration
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, especially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
You may provide a JAAS login.conf file:
1
2
3
4
5
6
7
8
jcifs.spnego.initiate {
com.sun.security.auth.module.Krb5LoginModule \
required storeKey=true useKeyTab=true keyTab="/home/cas/kerberos/myspnaccount.keytab";
};
jcifs.spnego.accept {
com.sun.security.auth.module.Krb5LoginModule \
required storeKey=true useKeyTab=true keyTab="/home/cas/kerberos/myspnaccount.keytab";
};
Client Selection Strategy
CAS provides a set of components that attempt to activate the SPNEGO flow conditionally,
in case deployers need a configurable way to decide whether SPNEGO should be applied to the
current authentication/browser request. The state that is available to the webflow
is evaluateClientRequest which will attempt to start SPNEGO authentication
or resume normally, depending on the client action strategy chosen below.
The following settings and properties are available from the CAS configuration catalog:
cas.authn.spnego.alternative-remote-host-attributeAlternative header name to use in order to find the host address.
alternateRemoteHeaderAlternative header name to use in order to find the host address.
cas.authn.spnego.dns-timeoutWhen validating clients, specifies the DNS timeout used to look up an address.
PT2SWhen validating clients, specifies the DNS timeout used to look up an address.
cas.authn.spnego.host-name-client-action-strategyThe bean id of a webflow action whose job is to evaluate the client host to see if the request is authorized for spnego.
hostnameSpnegoClientActionThe bean id of a webflow action whose job is to evaluate the client host to see if the request is authorized for spnego. Supported strategies include hostnameSpnegoClientAction where CAS checks to see if the request’s remote hostname matches a predefine pattern. and ldapSpnegoClientAction where CAS checks an LDAP instance for the remote hostname, to locate a pre-defined attribute whose mere existence would allow the webflow to resume to SPNEGO.
cas.authn.spnego.host-name-pattern-stringA regex pattern that indicates whether the client host name is allowed for spnego.
.+A regex pattern that indicates whether the client host name is allowed for spnego.
cas.authn.spnego.ips-to-check-patternA regex pattern that indicates whether the client IP is allowed for spnego.
127.+A regex pattern that indicates whether the client IP is allowed for spnego.
Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.
Notes on configuration
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, especially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
By Remote IP
Checks to see if the request’s remote ip address matches a predefine pattern.
By Hostname
Checks to see if the request’s remote hostname matches a predefine pattern.
By LDAP Attribute
Checks an LDAP instance for the remote hostname, to locate a pre-defined attribute whose mere existence would allow the webflow to resume to SPNEGO.
The following settings and properties are available from the CAS configuration catalog:
cas.authn.spnego.ldap.base-dnBase DN to use.
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.
cas.authn.spnego.ldap.bind-credentialThe bind credential to use when connecting to LDAP.
The bind credential to use when connecting to LDAP.
cas.authn.spnego.ldap.bind-dnThe bind DN to use when connecting to LDAP.
-
bindDn/bindCredentialprovided - Use the provided credentials to bind when initializing connections. -
bindDn/bindCredentialset to*- Use a fast-bind strategy to initialize the pool. -
bindDn/bindCredentialset to blank - Skip connection initializing; perform operations anonymously. - SASL mechanism provided - Use the given SASL mechanism to bind when initializing connections.
cas.authn.spnego.ldap.ldap-urlThe LDAP url to the server.
The LDAP url to the server. More than one may be specified, separated by space and/or comma.
cas.authn.spnego.ldap.search-filterUser filter to use for searching.
User filter to use for searching. Syntax is cn={user} or cn={0}.
You may also provide an external groovy script in the syntax of file:/path/to/GroovyScript.groovy to fully build the final filter template dynamically.
cas.authn.spnego.ldap.allow-multiple-dnsWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
falseWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
cas.authn.spnego.ldap.allow-multiple-entriesSet if multiple Entries are allowed.
falseSet if multiple Entries are allowed.
cas.authn.spnego.ldap.binary-attributesIndicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
Indicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
cas.authn.spnego.ldap.block-wait-timeThe length of time the pool will block.
PT3SThe 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
cas.authn.spnego.ldap.connect-timeoutSets the maximum amount of time that connects will block.
PT5SSets the maximum amount of time that connects will block.
cas.authn.spnego.ldap.connection-strategyIf multiple URLs are provided as the ldapURL this describes how each URL will be processed.
-
ACTIVE_PASSIVEFirst LDAP will be used for every request unless it fails and then the next shall be used. -
ROUND_ROBINFor each new connection the next url in the list will be used. -
RANDOMFor each new connection a random LDAP url will be selected. -
DNS_SRVLDAP urls based on DNS SRV records of the configured/given LDAP url will be used.
cas.authn.spnego.ldap.disable-poolingWhether to use a pooled connection factory in components.
falseWhether to use a pooled connection factory in components.
cas.authn.spnego.ldap.fail-fastAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
trueAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
cas.authn.spnego.ldap.follow-referralsSet if search referrals should be followed.
trueSet if search referrals should be followed.
cas.authn.spnego.ldap.hostname-verifierHostname verification options.
DEFAULT-
DEFAULT: Default option, forcing verification. -
ANY: Skip hostname verification and allow all.
cas.authn.spnego.ldap.idle-timeRemoves connections from the pool based on how long they have been idle in the available queue.
PT10MRemoves 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.
cas.authn.spnego.ldap.keystorePath to the keystore used for SSL connections.
Path to the keystore used for SSL connections. Typically contains SSL certificates for the LDAP server.
cas.authn.spnego.ldap.keystore-passwordKeystore password.
Keystore password.
cas.authn.spnego.ldap.keystore-typeThe type of keystore.
The type of keystore. PKCS12 or JKS. If left blank, defaults to the default keystore type indicated by the underlying Java platform.
cas.authn.spnego.ldap.max-pool-sizeMaximum LDAP connection pool size which the pool can use to grow.
10Maximum LDAP connection pool size which the pool can use to grow.
cas.authn.spnego.ldap.min-pool-sizeMinimum LDAP connection pool size.
3Minimum LDAP connection pool size. Size the pool should be initialized to and pruned to
cas.authn.spnego.ldap.nameName of the LDAP handler.
Name of the LDAP handler.
cas.authn.spnego.ldap.page-sizeRequest that the server return results in batches of a specific size.
0Request 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.
cas.authn.spnego.ldap.pool-passivatorYou 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.
BINDDIRECT 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.
cas.authn.spnego.ldap.prune-periodRemoves connections from the pool based on how long they have been idle in the available queue.
PT2HRemoves connections from the pool based on how long they have been idle in the available queue. Run the pruning process at the indicated interval.
cas.authn.spnego.ldap.response-timeoutDuration of time to wait for responses.
PT5SDuration of time to wait for responses.
cas.authn.spnego.ldap.sasl-authorization-idSASL authorization id.
SASL authorization id.
cas.authn.spnego.ldap.sasl-mechanismThe SASL mechanism.
The SASL mechanism.
cas.authn.spnego.ldap.sasl-mutual-authWhether SASL mutual authentication is enabled.
Whether SASL mutual authentication is enabled.
cas.authn.spnego.ldap.sasl-quality-of-protectionSASL quality of protected.
SASL quality of protected.
cas.authn.spnego.ldap.sasl-realmThe SASL realm.
The SASL realm.
cas.authn.spnego.ldap.sasl-security-strengthSASL security strength.
SASL security strength.
cas.authn.spnego.ldap.search-entry-handlersSearch handlers.
Search handlers.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-name-case-changeThe Attribute name case change.
The Attribute name case change.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-namesThe Attribute names.
The Attribute names.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.attribute-value-case-changeThe Attribute value case change.
The Attribute value case change.
cas.authn.spnego.ldap.search-entry-handlers[0].case-change.dn-case-changeThe Dn case change.
The Dn case change.
cas.authn.spnego.ldap.search-entry-handlers[0].dn-attribute.add-if-existsThe Add if exists.
The Add if exists.
cas.authn.spnego.ldap.search-entry-handlers[0].dn-attribute.dn-attribute-nameThe Dn attribute name.
entryDNThe Dn attribute name.
cas.authn.spnego.ldap.search-entry-handlers[0].merge-attribute.attribute-namesThe Attribute names.
The Attribute names.
cas.authn.spnego.ldap.search-entry-handlers[0].merge-attribute.merge-attribute-nameThe Merge attribute name.
The Merge attribute name.
cas.authn.spnego.ldap.search-entry-handlers[0].primary-group-id.base-dnThe Base dn.
The Base dn.
cas.authn.spnego.ldap.search-entry-handlers[0].primary-group-id.group-filterThe Group filter.
(&(objectClass=group)(objectSid={0}))The Group filter.
cas.authn.spnego.ldap.search-entry-handlers[0].recursive.merge-attributesThe Merge attributes.
The Merge attributes.
cas.authn.spnego.ldap.search-entry-handlers[0].recursive.search-attributeThe Search attribute.
The Search attribute.
cas.authn.spnego.ldap.search-entry-handlers[0].search-referral.limitThe default referral limit.
10The default referral limit.
cas.authn.spnego.ldap.search-entry-handlers[0].search-result.limitThe default referral limit.
10The default referral limit.
cas.authn.spnego.ldap.search-entry-handlers[0].typeThe type of search entry handler to choose.
-
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 theobjectGUIDattribute fetching and conversion. -
OBJECT_SID: Object sid search entry handler. Handles theobjectSidattribute 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 thememberOfattribute 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.
cas.authn.spnego.ldap.subtree-searchWhether subtree searching is allowed.
trueWhether subtree searching is allowed.
cas.authn.spnego.ldap.trust-certificatesPath of the trust certificates to use for the SSL connection.
Path of the trust certificates to use for the SSL connection. Ignores keystore-related settings when activated and used.
cas.authn.spnego.ldap.trust-managerTrust Manager options.
-
DEFAULT: Enable and force the default JVM trust managers. -
ANY: Trust any client or server.
cas.authn.spnego.ldap.trust-storePath to the keystore used to determine which certificates or certificate authorities should be trusted.
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.
cas.authn.spnego.ldap.trust-store-passwordPassword needed to open the truststore.
Password needed to open the truststore.
cas.authn.spnego.ldap.trust-store-typeThe type of trust keystore that determines which certificates or certificate authorities are trusted.
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.
cas.authn.spnego.ldap.use-start-tlsWhether TLS should be used and enabled when establishing the connection.
falseWhether TLS should be used and enabled when establishing the connection.
cas.authn.spnego.ldap.validate-on-checkoutWhether connections should be validated when loaned out from the pool.
trueWhether connections should be validated when loaned out from the pool.
cas.authn.spnego.ldap.validate-periodPeriod at which pool should be validated.
PT5MPeriod at which pool should be validated.
cas.authn.spnego.ldap.validate-periodicallyWhether connections should be validated periodically when the pool is idle.
trueWhether connections should be validated periodically when the pool is idle.
cas.authn.spnego.ldap.validate-timeoutPeriod at which validation operations may time out.
PT5SPeriod at which validation operations may time out.
cas.authn.spnego.ldap.validator.attribute-nameAttribute name to use for the compare validator.
objectClassAttribute name to use for the compare validator.
cas.authn.spnego.ldap.validator.attribute-valueAttribute values to use for the compare validator.
topAttribute values to use for the compare validator.
cas.authn.spnego.ldap.validator.base-dnBase DN to use for the search request of the search validator.
Base DN to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.dnDN to compare to use for the compare validator.
DN to compare to use for the compare validator.
cas.authn.spnego.ldap.validator.scopeSearch scope to use for the search request of the search validator.
OBJECTSearch scope to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.search-filterSearch filter to use for the search request of the search validator.
(objectClass=*)Search filter to use for the search request of the search validator.
cas.authn.spnego.ldap.validator.typeDetermine the LDAP validator type.
searchDetermine the LDAP validator type.
-
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.
cas.authn.spnego.spnego-attribute-nameIn case LDAP is used to validate clients, this is the attribute that indicates the host.
distinguishedNameIn case LDAP is used to validate clients, this is the attribute that indicates the host.
Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.
LDAP & Active Directory
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.
Notes on configuration
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, especially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
Logging
To enable additional logging, configure the log4j configuration file to add the following levels:
1
2
3
4
5
6
...
<Logger name="jcifs.spnego" level="debug" additivity="false">
<AppenderRef ref="casConsole"/>
<AppenderRef ref="casFile"/>
</Logger>
...
Troubleshooting
- Failure unspecified at GSS-API level
1
2
3
4
5
6
7
8
9
10
11
Caused by: GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - AES256 CTS mode with HMAC SHA1-96)
at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Unknown Source)
at sun.security.jgss.GSSContextImpl.acceptSecContext(Unknown Source)
at sun.security.jgss.GSSContextImpl.acceptSecContext(Unknown Source)
... 280 more
Caused by: KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt
AP REP - AES256 CTS mode with HMAC SHA1-96
at sun.security.krb5.KrbApReq.authenticate(Unknown Source)
at sun.security.krb5.KrbApReq.<init>(Unknown Source)
at sun.security.jgss.krb5.InitSecContextToken.<init>(Unknown Source)
... 283 more
It’s very likely that you have the wrong path to .keytab file. The KVNO in the keytab file must be identical with the KVNO stored in the Active Directory. Active Directory is raising the KVNO with every execution of ktpass, as part of its msDS-KeyVersionNumber.
Other possible causes include:
- The service principal in the in the CAS configuration is not identical with that from the keytab. (param
/princfrom ktpass) - There is no key for the
enctypesent with the ticket by Active Directory. (param/cryptofromktpassand set in thekrb5.conf/permitted_enctypes+default_tkt_enctypes). - The KVNO from the ticket is different than the KVNO in the keytab (param
/kvnofromktpass).