Password Management - Password Reset

CAS may allow users to reset their passwords voluntarily. Those who have forgotten their account password may receive a secure link with a time-based expiration policy at their registered email address and/or phone. The link will allow the user to provide answers to his/her pre-defined security questions, which if successfully done, will allow the user to next reset their password and login again. You may also specify a pattern for accepted passwords.

By default, after a user has successfully changed their password they will be redirected to the login screen to enter their new password and log in. CAS can also be configured to automatically log the user in after a successful change. This behavior can be altered via CAS settings.

CAS login requests also accept a special doChangePassword query parameter that allows one to forcefully launch into the password reset flow. Specifying this parameter with a value of true can be particularly useful in the presence of existing single sign-on sessions when the user who already has logged in wants to change their password.

Configuration

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

cas.authn.pm.reset.confirmation-mail.attribute-namePrincipal attribute names that indicates the destination email address for this message.
no default
RequiredSpEL

Principal attribute names that indicates the destination email address for this message. The attributes must already be resolved and available to the CAS principal. When multiple attributes are specified, each attribute is then examined against the available CAS principal to locate the email address value, which may result in multiple emails being sent.

Type
List<String>
Default
none
Defined by
EmailProperties
Supports
Spring Expression Language
cas.authn.pm.reset.confirmation-mail.fromEmail from address.
no default
Required

Email from address.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.subjectEmail subject line.
no default
RequiredSpEL

Email subject line.

The subject can either be defined verbatim, or it may point to a message key in the language bundle using the syntax #{subject-language-key}. This key should point to a valid message defined in the appropriate language bundle that is then picked up via the active locale. In case where the language code cannot resolve the real subject, a default subject value would be used.

Type
String
Default
none
Defined by
EmailProperties
Supports
Spring Expression Language
cas.authn.pm.reset.crypto.encryption.keyThe encryption key is a string whose length is defined by the encryption key size setting.
no default
RequiredSpEL

The encryption key is a string whose length is defined by the encryption key size setting.

Type
String
Default
none
Defined by
EncryptionJwtCryptoProperties
Supports
Spring Expression Language
cas.authn.pm.reset.crypto.signing.keyThe signing key is a string whose length is defined by the signing key size setting.
no default
RequiredSpEL

The signing key is a string whose length is defined by the signing key size setting.

Type
String
Default
none
Defined by
SigningJwtCryptoProperties
Supports
Spring Expression Language
cas.authn.pm.reset.mail.attribute-namePrincipal attribute names that indicates the destination email address for this message.
no default
RequiredSpEL

Principal attribute names that indicates the destination email address for this message. The attributes must already be resolved and available to the CAS principal. When multiple attributes are specified, each attribute is then examined against the available CAS principal to locate the email address value, which may result in multiple emails being sent.

Type
List<String>
Default
none
Defined by
EmailProperties
Supports
Spring Expression Language
cas.authn.pm.reset.mail.fromEmail from address.
no default
Required

Email from address.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.mail.subjectEmail subject line.
no default
RequiredSpEL

Email subject line.

The subject can either be defined verbatim, or it may point to a message key in the language bundle using the syntax #{subject-language-key}. This key should point to a valid message defined in the appropriate language bundle that is then picked up via the active locale. In case where the language code cannot resolve the real subject, a default subject value would be used.

Type
String
Default
none
Defined by
EmailProperties
Supports
Spring Expression Language
cas.authn.pm.reset.sms.attribute-namePrincipal attribute names that indicates the destination phone number for this SMS message.
no default
RequiredSpEL

Principal attribute names that indicates the destination phone number for this SMS message. The attribute must already be resolved and available to the CAS principal.

Type
List<String>
Default
none
Defined by
SmsProperties
Supports
Spring Expression Language
cas.authn.pm.reset.sms.fromThe from address for the message.
no default
Required

The from address for the message.

Type
String
Default
none
Defined by
SmsProperties
cas.authn.pm.reset.sms.textThe body of the SMS message.
no default
Required

The body of the SMS message.

Type
String
Default
none
Defined by
SmsProperties
cas.authn.pm.reset.confirmation-mail.bccEmail BCC address, if any.
no default

Email BCC address, if any.

Type
List<String>
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.ccEmail CC address, if any.
no default

Email CC address, if any.

Type
List<String>
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.htmlIndicate whether the message body should be evaluated as HTML text.
false

Indicate whether the message body should be evaluated as HTML text. The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Boolean
Default
false
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.prioritySet the priority ( X-Priority header) of the message.
1

Set the priority (X-Priority header) of the message. Values: 1 (Highest), 2 (High), 3 (Normal), 4 (Low), 5 (Lowest). The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Integer
Default
1
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.reply-toEmail Reply-To address, if any.
no default

Email Reply-To address, if any.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.textEmail message body.
no default

Email message body. Could be plain text or a reference to an external file that would serve as a template.

If specified as a path to an external file with an extension .gtemplate, then the email message body would be processed using the Groovy template engine. The template engine uses JSP style <% %> script and <%= %> expression syntax or GString style expressions. The variable out is bound to the writer that the template is being written to.

If using plain text, the contents are processed for string substitution candidates using named variables. For example, you may refer to an expected url variable in the email text via ${url}, or use ${token} to locate the token variable. In certain cases, additional parameters are passed to the email body processor that might include authentication and/or principal attributes, the available locale, client http information, etc.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.confirmation-mail.validate-addressesSet whether to validate all addresses which get passed to this helper.
false

Set whether to validate all addresses which get passed to this helper. The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Boolean
Default
false
Defined by
EmailProperties
cas.authn.pm.reset.crypto.algThe signing/encryption algorithm to use.
no default

The signing/encryption algorithm to use.

Type
String
Default
none
Defined by
EncryptionJwtSigningJwtCryptographyProperties
cas.authn.pm.reset.crypto.enabledWhether crypto operations are enabled.
true

Whether crypto operations are enabled.

Type
Boolean
Default
true
Defined by
EncryptionJwtSigningJwtCryptographyProperties
cas.authn.pm.reset.crypto.encryption.key-sizeThe encryption key size.
512

The encryption key size.

Type
Integer
Default
512
Defined by
EncryptionJwtCryptoProperties
cas.authn.pm.reset.crypto.signing.key-sizeThe signing key size.
512

The signing key size.

Type
Integer
Default
512
Defined by
SigningJwtCryptoProperties
cas.authn.pm.reset.crypto.strategy-typeControl the cipher sequence of operations.
ENCRYPT_AND_SIGN
Control the cipher sequence of operations. The accepted values are:
  • ENCRYPT_AND_SIGN: Encrypt the value first, and then sign.
  • SIGN_AND_ENCRYPT: Sign the value first, and then encrypt.
Type
String
Default
ENCRYPT_AND_SIGN
Defined by
EncryptionJwtSigningJwtCryptographyProperties
cas.authn.pm.reset.expirationHow long in minutes should the password expiration link remain valid.
PT1M
Duration

How long in minutes should the password expiration link remain valid.

Type
String
Default
PT1M
Defined by
ResetPasswordManagementProperties
cas.authn.pm.reset.include-client-ip-addressWhether the Password Management Token will contain the client IP Address.
true

Whether the Password Management Token will contain the client IP Address.

Type
Boolean
Default
true
Defined by
ResetPasswordManagementProperties
cas.authn.pm.reset.include-server-ip-addressWhether the Password Management Token will contain the server IP Address.
true

Whether the Password Management Token will contain the server IP Address.

Type
Boolean
Default
true
Defined by
ResetPasswordManagementProperties
cas.authn.pm.reset.mail.bccEmail BCC address, if any.
no default

Email BCC address, if any.

Type
List<String>
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.mail.ccEmail CC address, if any.
no default

Email CC address, if any.

Type
List<String>
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.mail.htmlIndicate whether the message body should be evaluated as HTML text.
false

Indicate whether the message body should be evaluated as HTML text. The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Boolean
Default
false
Defined by
EmailProperties
cas.authn.pm.reset.mail.prioritySet the priority ( X-Priority header) of the message.
1

Set the priority (X-Priority header) of the message. Values: 1 (Highest), 2 (High), 3 (Normal), 4 (Low), 5 (Lowest). The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Integer
Default
1
Defined by
EmailProperties
cas.authn.pm.reset.mail.reply-toEmail Reply-To address, if any.
no default

Email Reply-To address, if any.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.mail.textEmail message body.
no default

Email message body. Could be plain text or a reference to an external file that would serve as a template.

If specified as a path to an external file with an extension .gtemplate, then the email message body would be processed using the Groovy template engine. The template engine uses JSP style <% %> script and <%= %> expression syntax or GString style expressions. The variable out is bound to the writer that the template is being written to.

If using plain text, the contents are processed for string substitution candidates using named variables. For example, you may refer to an expected url variable in the email text via ${url}, or use ${token} to locate the token variable. In certain cases, additional parameters are passed to the email body processor that might include authentication and/or principal attributes, the available locale, client http information, etc.

Type
String
Default
none
Defined by
EmailProperties
cas.authn.pm.reset.mail.validate-addressesSet whether to validate all addresses which get passed to this helper.
false

Set whether to validate all addresses which get passed to this helper. The application of this setting depends on the email provider implementation and may not be fully supported everywhere. This is typically relevant for the default org.springframework.mail.javamail.JavaMailSender.

Type
Boolean
Default
false
Defined by
EmailProperties
cas.authn.pm.reset.multifactor-authentication-enabledControls whether password reset operations must activate and support a multifactor authentication flow based on the set of available MFA providers that are configured and active, before reset instructions can be share...
true

Controls whether password reset operations must activate and support a multifactor authentication flow based on the set of available MFA providers that are configured and active, before reset instructions can be shared and sent.

Type
Boolean
Default
true
Defined by
ResetPasswordManagementProperties
cas.authn.pm.reset.number-of-usesHow many times you can use the password reset link.
-1

How many times you can use the password reset link. Strictly lower than 1 means infinite.

Type
Integer
Default
-1
Defined by
ResetPasswordManagementProperties
cas.authn.pm.reset.security-questions-enabledWhether reset operations require security questions, or should they be marked as optional.
true

Whether reset operations require security questions, or should they be marked as optional.

Type
Boolean
Default
true
Defined by
ResetPasswordManagementProperties

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.

Signing & encryption

This CAS feature is able to accept signing and encryption crypto keys. In most scenarios if keys are not provided, CAS will auto-generate them. The following instructions apply if you wish to manually and beforehand create the signing and encryption keys.

Note that if you are asked to create a JWK of a certain size for the key, you are to use the following set of commands to generate the token:

1
2
wget https://raw.githubusercontent.com/apereo/cas/master/etc/jwk-gen.jar
java -jar jwk-gen.jar -t oct -s [size]

The outcome would be similar to:

1
2
3
4
5
{
  "kty": "oct",
  "kid": "...",
  "k": "..."
}

The generated value for k needs to be assigned to the relevant CAS settings. Note that keys generated via the above algorithm are processed by CAS using the Advanced Encryption Standard (AES) algorithm which is a specification for the encryption of electronic data established by the U.S. National Institute of Standards and Technology.


Email servers

The following settings may also need to be defined to describe the mail server settings:

spring.mail.default-encodingDefault MimeMessage encoding.
UTF-8
Third party

Default MimeMessage encoding.

Type
Charset
Default
UTF-8
Defined by
MailProperties
spring.mail.hostSMTP server host.
no default
Third party

SMTP server host. For instance, 'smtp.example.com'.

Type
String
Default
none
Defined by
MailProperties
spring.mail.jndi-nameSession JNDI name.
no default
Third party

Session JNDI name. When set, takes precedence over other Session settings.

Type
String
Default
none
Defined by
MailProperties
spring.mail.passwordLogin password of the SMTP server.
no default
Third party

Login password of the SMTP server.

Type
String
Default
none
Defined by
MailProperties
spring.mail.portSMTP server port.
no default
Third party

SMTP server port.

Type
Integer
Default
none
Defined by
MailProperties
spring.mail.propertiesAdditional JavaMail Session properties.
no default
Third party

Additional JavaMail Session properties.

Type
Map<String,String>
Default
none
Defined by
MailProperties
spring.mail.protocolProtocol used by the SMTP server.
smtp
Third party

Protocol used by the SMTP server.

Type
String
Default
smtp
Defined by
MailProperties
spring.mail.ssl.bundleSSL bundle name.
no default
Third party

SSL bundle name. If set, 'mail.(protocol).ssl.socketFactory' property is set to an SSLSocketFactory obtained from the corresponding SSL bundle.

Note that the STARTTLS command can use the corresponding SSLSocketFactory, even if the 'mail.(protocol).ssl.enable' property is not set.

Type
String
Default
none
Defined by
MailProperties$Ssl
spring.mail.ssl.enabledWhether to enable SSL support.
false
Third party

Whether to enable SSL support. If enabled, 'mail.(protocol).ssl.enable' property is set to 'true'.

Type
Boolean
Default
false
Defined by
MailProperties$Ssl
spring.mail.ssl.verify-hostnameWhether to enable hostname verification.
true
Third party

Whether to enable hostname verification.

Type
Boolean
Default
true
Defined by
MailProperties$Ssl
spring.mail.test-connectionWhether to test that the mail server is available on startup.
false
Third party

Whether to test that the mail server is available on startup.

Type
Boolean
Default
false
Defined by
MailSenderValidatorAutoConfiguration
spring.mail.usernameLogin user of the SMTP server.
no default
Third party

Login user of the SMTP server.

Type
String
Default
none
Defined by
MailProperties
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.

:information_source: Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

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.

To learn more about available notification options, please see this guide or this guide.

reCAPTCHA Integration

Password reset attempts can be protected and integrated with Google reCAPTCHA. This requires the presence of reCAPTCHA settings for the basic integration and instructing the password management flow to turn on and verify requests via reCAPTCHA.

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

cas.authn.pm.google-recaptcha.enabledWhether reCAPTCHA should be enabled.
true
Required

Whether reCAPTCHA should be enabled.

Type
Boolean
Default
true
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.scoreGoogle reCAPTCHA v3 returns a score (1.0 is very likely a good interaction, 0.0 is very likely a bot). reCAPTCHA learns by seeing real traffic on your site.
0.5
Required

Google reCAPTCHA v3 returns a score (1.0 is very likely a good interaction, 0.0 is very likely a bot). reCAPTCHA learns by seeing real traffic on your site. For this reason, scores in a staging environment or soon after implementing may differ from production. As reCAPTCHA v3 doesn't ever interrupt the user flow, you can first run reCAPTCHA without taking action and then decide on thresholds by looking at your traffic in the admin console. By default, you can use a threshold of 0.5.

Type
Double
Default
0.5
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.secretThe reCAPTCHA site secret.
no default
Required

The reCAPTCHA site secret.

Type
String
Default
none
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.site-keyThe reCAPTCHA site key.
no default
RequiredSpEL

The reCAPTCHA site key.

Type
String
Default
none
Defined by
GoogleRecaptchaProperties
Supports
Spring Expression Language
cas.authn.pm.google-recaptcha.activate-for-ip-address-patternA regular expression pattern to indicate that captcha should be activated when the remote IP address matches this pattern, and otherwise skipped and disabled.
no default
Regex

A regular expression pattern to indicate that captcha should be activated when the remote IP address matches this pattern, and otherwise skipped and disabled.

Type
String
Default
none
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.headersHeaders, defined as a Map , to include in the request when making the verification call to the recaptcha API.
no default

Headers, defined as a Map, to include in the request when making the verification call to the recaptcha API.

Type
Map<String,String>
Default
none
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.invisibleWhether google reCAPTCHA invisible should be enabled.
false

Whether google reCAPTCHA invisible should be enabled.

Type
Boolean
Default
false
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.positionThe google reCAPTCHA badge position (only if invisible is enabled).
bottomright
The google reCAPTCHA badge position (only if invisible is enabled). Accepted values are:
  • bottomright: bottom right corner, default value.
  • bottomleft: bottom left corner
  • inline: allows one to control the CSS.
Type
String
Default
bottomright
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.verify-urlThe reCAPTCHA endpoint for verification of the reCAPTCHA response.
https://www.google.com/recaptcha/api/siteverify
The reCAPTCHA endpoint for verification of the reCAPTCHA response. The endpoint is specific to the reCAPTCHA provider:
  • For Google reCAPTCHA, the endpoint is https://www.google.com/recaptcha/api/siteverify.
  • For hCaptcha, the endpoint is https://hcaptcha.com/siteverify.
  • For Turnstile, the endpoint is https://challenges.cloudflare.com/turnstile/v0/siteverify.
Type
String
Default
https://www.google.com/recaptcha/api/siteverify
Defined by
GoogleRecaptchaProperties
cas.authn.pm.google-recaptcha.versionIndicate the version of the recaptcha api.
GOOGLE_RECAPTCHA_V2
Indicate the version of the recaptcha api. Available values are as follows:
  • GOOGLE_RECAPTCHA_V2: V2 version of the recaptcha API.
  • GOOGLE_RECAPTCHA_V3: V3 version of the recaptcha API.
  • HCAPTCHA: hCaptcha is an alternative to reCAPTCHA that requires website visitors to label images as part of its business model. The provider is more focused on manual image recognition challenges. It is a image classification task based CAPTCHA provider employing visual challenges like identifying objects.
  • TURNSTILE: Offers a CAPTCHA alternative by Cloudflare that prioritizes user experience and privacy. Turnstile delivers frustration-free, CAPTCHA-free web experiences to website visitors - with just a simple snippet of free code. Moreover, Turnstile stops abuse and confirms visitors are real without the data privacy concerns or awful user experience of CAPTCHAs.
  • FRIENDLY_CAPTCHA: Friendly captcha is a European alternative, accessible and GDPR compliant.
Type
GoogleRecaptchaProperties.RecaptchaVersions
Default
GOOGLE_RECAPTCHA_V2
Defined by
GoogleRecaptchaProperties

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.

:information_source: Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

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.

Actuator Endpoints

The following endpoints are provided by CAS:

passwordManagement
CAS endpoint3 operationsNot exposed by defaultcas-server-support-pm-webflow
1

Include the module that provides this endpoint in the WAR overlay:

1
2
3
4
5
<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-pm-webflow</artifactId>
    <version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-pm-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-pm-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-pm-webflow"
}
2

Turn the endpoint on and expose it over the web. One entry covers every operation. By default only info, health and status are exposed.

1
2
management.endpoint.passwordManagement.access=UNRESTRICTED
management.endpoints.web.exposure.include=passwordManagement

Endpoints may be mapped to other paths. For example, to serve health at healthcheck:

1
management.endpoints.web.path-mapping.health=healthcheck