Localization

The CAS Web application includes a number of localized message files:

  • English (US)
  • Spanish
  • French
  • Russian
  • Dutch (Netherlands)
  • Swedish (Svenskt)
  • Italian (Italiano)
  • Urdu
  • Chinese (Simplified)
  • German (Deutsch)
  • Japanese
  • Croatian
  • Czech
  • Slovenian
  • Polish
  • Portuguese (Brazil)
  • Turkish
  • Farsi
  • Arabic

In order to “invoke” a specific language for the UI, the /login endpoint may be passed a locale parameter as such:

1

https://cas.server.org/login?locale=it
Usage Warning!

Note that not all languages are complete and accurate across CAS server releases as translations are entirely dependent upon community contributions. For an accurate and complete list of localized messages, always refer to the English language bundle.

Configuration

All message bundles are marked under messages_xx.properties files at src/main/resources. The default language bundle is for the English language and is thus called messages.properties. If there are any custom messages that need to be presented into views, they may also be formatted under custom_messages.properties files.

In the event that the code is not found in the activated resource bundle, the code itself will be used verbatim.

Localization

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

The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.

The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This flag indicates that the presence of the setting is not immediately necessary in the end-user CAS configuration, because a default value is assigned or the activation of the feature is not conditionally controlled by the setting value.

  • cas.locale.cookie.allowed-ip-addresses-pattern=

    • A regular expression pattern that indicates the set of allowed IP addresses, when #isPinToSession() is cofigured. In the event that there is a mismatch between the cookie IP address and the current request-provided IP address (i.e. network switches, VPN, etc), the cookie can still be considered valid if the new IP address matches the pattern specified here.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.comment=CAS Cookie

    • CAS Cookie comment, describes the cookie's usage and purpose.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.domain=

    • Cookie domain. Specifies the domain within which this cookie should be presented. The form of the domain name is specified by RFC 2965. A domain name begins with a dot (.foo.com) and means that the cookie is visible to servers in a specified Domain Name System (DNS) zone (for example, www.foo.com, but not a.b.foo.com). By default, cookies are only returned to the server that sent them.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.http-only=true

    • true if this cookie contains the HttpOnly attribute. This means that the cookie should not be accessible to scripting engines, like javascript.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.max-age=-1

    • The maximum age of the cookie, specified in seconds. By default, -1 indicating the cookie will persist until browser shutdown. A positive value indicates that the cookie will expire after that many seconds have passed. Note that the value is the maximum age when the cookie will expire, not the cookie's current age. A negative value means that the cookie is not stored persistently and will be deleted when the Web browser exits. A zero value causes the cookie to be deleted.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.name=

    • Cookie name. Constructs a cookie with a specified name and value. The name must conform to RFC 2965. That means it can contain only ASCII alphanumeric characters and cannot contain commas, semicolons, or white space or begin with a $ character. The cookie's name cannot be changed after creation. By default, cookies are created according to the RFC 2965 cookie specification. Cookie names are automatically calculated assigned by CAS at runtime, and there is usually no need to customize the name or assign it a different value unless a special use case warrants the change.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.path=

    • Cookie path. Specifies a path for the cookie to which the client should return the cookie. The cookie is visible to all the pages in the directory you specify, and all the pages in that directory's subdirectories. A cookie's path must include the servlet that set the cookie, for example, /catalog, which makes the cookie visible to all directories on the server under /catalog. Consult RFC 2965 (available on the Internet) for more information on setting path names for cookies.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.pin-to-session=true

    • When generating cookie values, determine whether the value should be compounded and signed with the properties of the current session, such as IP address, user-agent, etc.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.same-site-policy=

    • If a cookie is only intended to be accessed in a first party context, the developer has the option to apply one of settings SameSite=Lax or SameSite=Strict or SameSite=None to prevent external access.

    To safeguard more websites and their users, the new secure-by-default model assumes all cookies should be protected from external access unless otherwise specified. Developers must use a new cookie setting, SameSite=None, to designate cookies for cross-site access. When the SameSite=None attribute is present, an additional Secure attribute is used so cross-site cookies can only be accessed over HTTPS connections.

    Accepted values are:

    • Lax
    • Strict
    • None
    • Off: Disable the generation of the SamSite cookie attribute altogether.
    • Fully qualified name of a class that implements org.apereo.cas.web.cookie.CookieSameSitePolicy

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.cookie.secure=true

    • True if sending this cookie should be restricted to a secure protocol, or false if the it can be sent using any protocol.

    org.apereo.cas.configuration.model.core.web.LocaleCookieProperties.
  • cas.locale.default-value=en

    • Default locale.

    org.apereo.cas.configuration.model.core.web.LocaleProperties.
  • cas.locale.force-default-locale=false

    • When set to true, locale resolution via request parameters and such is ignored and the locale default value is always enforced.

    org.apereo.cas.configuration.model.core.web.LocaleProperties.
  • cas.locale.param-name=locale

    • Parameter name to use when switching locales.

    org.apereo.cas.configuration.model.core.web.LocaleProperties.