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.
Inwebo/TrustBuilder Multifactor Authentication
You can secure your CAS server with a second factor provided by Inwebo.

In 2023 and one year after the strategic acquisition of TrustBuilder by inWebo, the two companies have now officially become one and are rebranded as TrustBuilder
A complete documentation of this integration can be found on the Inwebo documentation website.
Apart from this CAS integration, notice that this identity provider can provide more general authentication solutions.
Support is enabled by including the following module in the overlay:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-inwebo-mfa</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-inwebo-mfa:${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-inwebo-mfa"
}
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-inwebo-mfa"
}
The integration adds support for both push mobile/desktop and browser authentications (Virtual Authenticator or mAccess WEB).
Configuration
The following settings and properties are available from the CAS configuration catalog:
- Required
- Optional
- Signing & Encryption
- Hibernate & JDBC
- Email Servers
- LDAP & Active Directory
- Authentication
- Password Encoding
- Principal Transformation
- Password Policy
- Notes
cas.authn.mfa.inwebo.bypass.groovy.location=
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 .
CAS Property:
|
1 |
cas.authn.mfa.inwebo.bypass.groovy.location=... |
1
cas:
authn:
mfa:
inwebo:
bypass: "..." groovy:
location:
1
java -Dcas.authn.mfa.inwebo.bypass.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_MFA_INWEBO_BYPASS_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.mfa.inwebo.bypass.groovy.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.rest.url=
The endpoint URL to contact and retrieve attributes.
org.apereo.cas.configuration.model.support.mfa.RestfulMultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.rest.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.mfa.inwebo.bypass.rest.url=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." rest:
url:
1
java -Dcas.authn.mfa.inwebo.bypass.rest.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_MFA_INWEBO_BYPASS_REST_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.mfa.inwebo.bypass.rest.url="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.client-certificate.certificate.location=
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
.
org.apereo.cas.configuration.model.SpringResourceProperties.
CAS Property: cas.authn.mfa.inwebo.client-certificate.certificate.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.mfa.inwebo.client-certificate.certificate.location=...
1
cas:
authn:
mfa:
inwebo:
client-certificate: "..." certificate:
location:
1
java -Dcas.authn.mfa.inwebo.client-certificate.certificate.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_MFA_INWEBO_CLIENT_CERTIFICATE_CERTIFICATE_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.mfa.inwebo.client-certificate.certificate.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.client-certificate.passphrase=
The passphrase of the client certificate.
org.apereo.cas.configuration.model.core.util.ClientCertificateProperties.
CAS Property: cas.authn.mfa.inwebo.client-certificate.passphrase

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.mfa.inwebo.client-certificate.passphrase=...
1
cas:
authn:
mfa:
inwebo:
client-certificate: "..." passphrase:
1
java -Dcas.authn.mfa.inwebo.client-certificate.passphrase="..." -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_MFA_INWEBO_CLIENT_CERTIFICATE_PASSPHRASE="..."
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.mfa.inwebo.client-certificate.passphrase="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.service-id=
The Inwebo service id.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.service-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.mfa.inwebo.service-id=...
1
cas:
authn:
mfa:
inwebo:
service-id: "..."
1
java -Dcas.authn.mfa.inwebo.service-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_MFA_INWEBO_SERVICE_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.mfa.inwebo.service-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.site-alias=
The alias of the secured site.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.site-alias

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.mfa.inwebo.site-alias=...
1
cas:
authn:
mfa:
inwebo:
site-alias: "..."
1
java -Dcas.authn.mfa.inwebo.site-alias="..." -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_MFA_INWEBO_SITE_ALIAS="..."
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.mfa.inwebo.site-alias="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.authentication-attribute-name=
Skip multifactor authentication based on designated authentication attribute names.
CAS Property:
|
1 |
cas.authn.mfa.inwebo.bypass.authentication-attribute-name=... |
1
cas:
authn:
mfa:
inwebo:
bypass: "..." authentication-attribute-name:
1
java -Dcas.authn.mfa.inwebo.bypass.authentication-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_MFA_INWEBO_BYPASS_AUTHENTICATION_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.mfa.inwebo.bypass.authentication-attribute-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.authentication-attribute-value=
Optionally, skip multifactor authentication based on designated authentication attribute values.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.authentication-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.mfa.inwebo.bypass.authentication-attribute-value=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." authentication-attribute-value:
1
java -Dcas.authn.mfa.inwebo.bypass.authentication-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_MFA_INWEBO_BYPASS_AUTHENTICATION_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.mfa.inwebo.bypass.authentication-attribute-value="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.authentication-handler-name=
Skip multifactor authentication depending on form of primary authentication execution. Specifically, skip multifactor if the a particular authentication handler noted by its name successfully is able to authenticate credentials in the primary factor.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.authentication-handler-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.mfa.inwebo.bypass.authentication-handler-name=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." authentication-handler-name:
1
java -Dcas.authn.mfa.inwebo.bypass.authentication-handler-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_MFA_INWEBO_BYPASS_AUTHENTICATION_HANDLER_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.mfa.inwebo.bypass.authentication-handler-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.authentication-method-name=
Skip multifactor authentication depending on method/form of primary authentication execution. Specifically, skip multifactor if the authentication method attribute collected as part of authentication metadata matches a certain value.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.authentication-method-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.mfa.inwebo.bypass.authentication-method-name=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." authentication-method-name:
1
java -Dcas.authn.mfa.inwebo.bypass.authentication-method-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_MFA_INWEBO_BYPASS_AUTHENTICATION_METHOD_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.mfa.inwebo.bypass.authentication-method-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.credential-class-type=
Skip multifactor authentication depending on form of primary credentials. Value must equal the fully qualified class name of the credential type.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.credential-class-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.mfa.inwebo.bypass.credential-class-type=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." credential-class-type:
1
java -Dcas.authn.mfa.inwebo.bypass.credential-class-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_MFA_INWEBO_BYPASS_CREDENTIAL_CLASS_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.mfa.inwebo.bypass.credential-class-type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.http-request-headers=
Skip multifactor authentication if the http request contains the defined header names. Header names may be comma-separated and can be regular expressions; values are ignored.
This settings supports regular expression patterns. [?].
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.http-request-headers

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.mfa.inwebo.bypass.http-request-headers=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." http-request-headers:
1
java -Dcas.authn.mfa.inwebo.bypass.http-request-headers="..." -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_MFA_INWEBO_BYPASS_HTTP_REQUEST_HEADERS="..."
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.mfa.inwebo.bypass.http-request-headers="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.http-request-remote-address=
Skip multifactor authentication if the http request's remote address or host matches the value defined here. The value may be specified as a regular expression.
This settings supports regular expression patterns. [?].
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.http-request-remote-address

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.mfa.inwebo.bypass.http-request-remote-address=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." http-request-remote-address:
1
java -Dcas.authn.mfa.inwebo.bypass.http-request-remote-address="..." -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_MFA_INWEBO_BYPASS_HTTP_REQUEST_REMOTE_ADDRESS="..."
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.mfa.inwebo.bypass.http-request-remote-address="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.principal-attribute-name=
Skip multifactor authentication based on designated principal attribute names.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.principal-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.mfa.inwebo.bypass.principal-attribute-name=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." principal-attribute-name:
1
java -Dcas.authn.mfa.inwebo.bypass.principal-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_MFA_INWEBO_BYPASS_PRINCIPAL_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.mfa.inwebo.bypass.principal-attribute-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.principal-attribute-value=
Optionally, skip multifactor authentication based on designated principal attribute values.
org.apereo.cas.configuration.model.support.mfa.MultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.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.mfa.inwebo.bypass.principal-attribute-value=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." principal-attribute-value:
1
java -Dcas.authn.mfa.inwebo.bypass.principal-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_MFA_INWEBO_BYPASS_PRINCIPAL_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.mfa.inwebo.bypass.principal-attribute-value="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.rest.basic-auth-password=
If REST endpoint is protected via basic authentication, specify the password for authentication.
org.apereo.cas.configuration.model.support.mfa.RestfulMultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.rest.basic-auth-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.mfa.inwebo.bypass.rest.basic-auth-password=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." rest:
basic-auth-password:
1
java -Dcas.authn.mfa.inwebo.bypass.rest.basic-auth-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_MFA_INWEBO_BYPASS_REST_BASIC_AUTH_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.mfa.inwebo.bypass.rest.basic-auth-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.rest.basic-auth-username=
If REST endpoint is protected via basic authentication, specify the username for authentication.
org.apereo.cas.configuration.model.support.mfa.RestfulMultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.rest.basic-auth-username

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.mfa.inwebo.bypass.rest.basic-auth-username=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." rest:
basic-auth-username:
1
java -Dcas.authn.mfa.inwebo.bypass.rest.basic-auth-username="..." -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_MFA_INWEBO_BYPASS_REST_BASIC_AUTH_USERNAME="..."
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.mfa.inwebo.bypass.rest.basic-auth-username="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.rest.headers=
Headers, defined as a Map, to include in the request when making the REST call. Will overwrite any header that CAS is pre-defined to send and include in the request. Key in the map should be the header name and the value in the map should be the header value.
org.apereo.cas.configuration.model.support.mfa.RestfulMultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.rest.headers

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.mfa.inwebo.bypass.rest.headers=...
1
cas:
authn:
mfa:
inwebo:
bypass: "..." rest:
headers:
1
java -Dcas.authn.mfa.inwebo.bypass.rest.headers="..." -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_MFA_INWEBO_BYPASS_REST_HEADERS="..."
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.mfa.inwebo.bypass.rest.headers="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.bypass.rest.method=GET
HTTP method to use when contacting the rest endpoint. Examples include GET, POST
, etc.
org.apereo.cas.configuration.model.support.mfa.RestfulMultifactorAuthenticationProviderBypassProperties.
CAS Property: cas.authn.mfa.inwebo.bypass.rest.method

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.mfa.inwebo.bypass.rest.method=GET
1
cas:
authn:
mfa:
inwebo:
bypass: "GET" rest:
method:
1
java -Dcas.authn.mfa.inwebo.bypass.rest.method="GET" -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_MFA_INWEBO_BYPASS_REST_METHOD="GET"
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.mfa.inwebo.bypass.rest.method="GET"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.browser-authenticator=VIRTUAL_AUTHENTICATOR
The browser authenticator to use (or none). Available values are as follows:
-
NONE
: No browser authentication. -
VIRTUAL_AUTHENTICATOR
: Virtual Authenticator browser authentication. -
M_ACCESS_WEB
: mAccessWeb browser authentication.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.browser-authenticator

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.mfa.inwebo.browser-authenticator=VIRTUAL_AUTHENTICATOR
1
cas:
authn:
mfa:
inwebo:
browser-authenticator: "VIRTUAL_AUTHENTICATOR"
1
java -Dcas.authn.mfa.inwebo.browser-authenticator="VIRTUAL_AUTHENTICATOR" -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_MFA_INWEBO_BROWSER_AUTHENTICATOR="VIRTUAL_AUTHENTICATOR"
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.mfa.inwebo.browser-authenticator="VIRTUAL_AUTHENTICATOR"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.console-admin-url=https://api.myinwebo.com/v2/services/ConsoleAdmin
Console admin API url.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.console-admin-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.mfa.inwebo.console-admin-url=https://api.myinwebo.com/v2/services/ConsoleAdmin
1
cas:
authn:
mfa:
inwebo:
console-admin-url: "https://api.myinwebo.com/v2/services/ConsoleAdmin"
1
java -Dcas.authn.mfa.inwebo.console-admin-url="https://api.myinwebo.com/v2/services/ConsoleAdmin" -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_MFA_INWEBO_CONSOLE_ADMIN_URL="https://api.myinwebo.com/v2/services/ConsoleAdmin"
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.mfa.inwebo.console-admin-url="https://api.myinwebo.com/v2/services/ConsoleAdmin"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.failure-mode=CLOSED
The failure mode policy for this MFA provider. The authentication policy by default supports fail-closed mode, which means that if you attempt to exercise a particular provider available to CAS and the provider cannot be reached, authentication will be stopped and an error will be displayed. You can of course change this behavior so that authentication proceeds without exercising the provider functionality, if that provider cannot respond. Each defined multifactor authentication provider can set its own failure mode policy. Failure modes set at this location will override the global failure mode, but defer to any failure mode set by the registered service. Available values are as follows:
-
OPEN
: Disallow MFA, proceed with authentication but don't communicate MFA to the RP. -
CLOSED
: Disallow MFA, block with authentication. -
PHANTOM
: Disallow MFA, proceed with authentication and communicate MFA to the RP. -
NONE
: Do not check for failure at all. -
UNDEFINED
: The default one indicating that no failure mode is set at all.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.failure-mode

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.mfa.inwebo.failure-mode=CLOSED
1
cas:
authn:
mfa:
inwebo:
failure-mode: "CLOSED"
1
java -Dcas.authn.mfa.inwebo.failure-mode="CLOSED" -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_MFA_INWEBO_FAILURE_MODE="CLOSED"
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.mfa.inwebo.failure-mode="CLOSED"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.id=
The identifier for the multifactor provider. In most cases, this need not be configured explicitly, unless multiple instances of the same provider type are configured in CAS.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.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.mfa.inwebo.id=...
1
cas:
authn:
mfa:
inwebo:
id: "..."
1
java -Dcas.authn.mfa.inwebo.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_MFA_INWEBO_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.mfa.inwebo.id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.name=
The name of the authentication handler used to verify credentials in MFA. Remember that if you have more than one authentication handler of the same type, the names must be defined uniquely for each authentication scheme. Failing to do so may force CAS to not register authentication handlers with a duplicate name.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.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.mfa.inwebo.name=...
1
cas:
authn:
mfa:
inwebo:
name: "..."
1
java -Dcas.authn.mfa.inwebo.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_MFA_INWEBO_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.mfa.inwebo.name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.order=
The order of the authentication handler in the chain.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.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.mfa.inwebo.order=...
1
cas:
authn:
mfa:
inwebo:
order: "..."
1
java -Dcas.authn.mfa.inwebo.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_MFA_INWEBO_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.mfa.inwebo.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.push-auto=true
Whether the push authentication should happen directly (without proposing the browser authentication if defined).
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.push-auto

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.mfa.inwebo.push-auto=true
1
cas:
authn:
mfa:
inwebo:
push-auto: "true"
1
java -Dcas.authn.mfa.inwebo.push-auto="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_MFA_INWEBO_PUSH_AUTO="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.mfa.inwebo.push-auto="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.push-enabled=true
Whether the push notification (mobile/desktop) is enabled.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.push-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.mfa.inwebo.push-enabled=true
1
cas:
authn:
mfa:
inwebo:
push-enabled: "true"
1
java -Dcas.authn.mfa.inwebo.push-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_MFA_INWEBO_PUSH_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.mfa.inwebo.push-enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.rank=0
At times, CAS needs to determine the correct provider when step-up authentication is required. Consider for a moment that CAS already has established an SSO session with/without a provider and has reached a level of authentication. Another incoming request attempts to exercise that SSO session with a different and often competing authentication requirement that may differ from the authentication level CAS has already established. Concretely, examples may be:
- CAS has achieved an SSO session, but a separate request now requires step-up authentication with DuoSecurity.
- CAS has achieved an SSO session with an authentication level satisfied by DuoSecurity, but a separate request now requires step-up authentication with YubiKey.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.rank

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.mfa.inwebo.rank=0
1
cas:
authn:
mfa:
inwebo:
rank: "0"
1
java -Dcas.authn.mfa.inwebo.rank="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_MFA_INWEBO_RANK="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.mfa.inwebo.rank="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.service-api-url=https://api.myinwebo.com/FS?
The service API url.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.service-api-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.mfa.inwebo.service-api-url=https://api.myinwebo.com/FS?
1
cas:
authn:
mfa:
inwebo:
service-api-url: "https://api.myinwebo.com/FS?"
1
java -Dcas.authn.mfa.inwebo.service-api-url="https://api.myinwebo.com/FS?" -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_MFA_INWEBO_SERVICE_API_URL="https://api.myinwebo.com/FS?"
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.mfa.inwebo.service-api-url="https://api.myinwebo.com/FS?"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.site-description=my secured site
The description of the secured site.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.site-description

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.mfa.inwebo.site-description=my secured site
1
cas:
authn:
mfa:
inwebo:
site-description: "my secured site"
1
java -Dcas.authn.mfa.inwebo.site-description="my secured site" -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_MFA_INWEBO_SITE_DESCRIPTION="my secured site"
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.mfa.inwebo.site-description="my secured site"
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.authn.mfa.inwebo.trusted-device-enabled=false
Indicates whether this provider should support trusted devices.
org.apereo.cas.configuration.model.support.mfa.InweboMultifactorAuthenticationProperties.
CAS Property: cas.authn.mfa.inwebo.trusted-device-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.mfa.inwebo.trusted-device-enabled=...
1
cas:
authn:
mfa:
inwebo:
trusted-device-enabled: "..."
1
java -Dcas.authn.mfa.inwebo.trusted-device-enabled="..." -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_MFA_INWEBO_TRUSTED_DEVICE_ENABLED="..."
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.mfa.inwebo.trusted-device-enabled="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
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.