Account Selection - Surrogate Authentication

The surrogate user selection can happen via the following ways.

• Preselected
• GUI
• Principal Attribute
• Wildcard

• This is the case where the surrogate user identity is known beforehand and is provided to CAS upon login using a special syntax. When entering credentials, the following syntax should be used:

  
  1
  
  [impersonated-userid][separator][primary-userid]
  
  

  For example, if you are casuser and you need to switch to jsmith as the surrogate (impersonated) user, the credential id or username provided to CAS would be jsmith+casuser where the separator is + and can be altered via the CAS configuration. CAS will first authenticate casuser as the primary user, and will then switch to jsmith when allowed.

• This is the case where the surrogate user identity is not known beforehand, and you wish to choose the account from a pre-populated list. When entering credentials, the following syntax should be used:

  
  1
  
  [separator][primary-userid]
  
  

  For example, if you are casuser and you need to locate the surrogate account to which you may want to switch, the credential id provided to CAS would be +casuser where the separator is + and can be altered via the CAS configuration. You will need to provide your own password of course.

• This option is similar to the Wildcard strategy, except that the impersonation logic is based off of a predefined principal attribute that is resolved and whose value(s) matches a certain regular expression pattern. That is, CAS can be configured to look for a specific attribute name for the primary/admin user and ensure that the attribute value matches a pattern to allow impersonation. The attribute is expected to be already be found and resolved for the admin user.

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

  • Required
  • Optional
  • Signing & Encryption
  • Hibernate & JDBC
  • Email Servers
  • Groovy Scripting
  • LDAP & Active Directory
  • Authentication
  • Password Encoding
  • Principal Transformation
  • Password Policy
  • Notes
  _{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. In other words, you should only include this field in your configuration if you need to modify the default value or if you need to turn on the feature controlled by the setting.}
  

  cas.authn.surrogate.core.principal-attribute-names= Impersonation can be authorized for all primary users/subjects carrying specific attributes with a predefined matching value specified via #principalAttributeValues. Needless to say, the attributes need to have been resolved for the primary principal prior to this step. Matching and comparison operations are case insensitive. org.apereo.cas.configuration.model.support.surrogate.SurrogateCoreAuthenticationProperties. How can I configure this property? CAS Property: cas.authn.surrogate.core.principal-attribute-names Configuration properties can be included and activated using the following strategies. 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. Java Property YAML Property System Property Environment Variable Command-line Argument CAS properties can be specified using the Java configuration property syntax in any and all .properties files: 1 cas.authn.surrogate.core.principal-attribute-names=... This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework. CAS properties can be specified using the YAML syntax: 1 cas: authn: surrogate: core: principal-attribute-names: "..." Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice. CAS properties can be passed to the CAS web application as system properties, when the application is launched: 1 java -Dcas.authn.surrogate.core.principal-attribute-names="..." -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as 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. CAS properties can specified as system environment variables before the CAS web application is launched: 1 2 3 export CAS_AUTHN_SURROGATE_CORE_PRINCIPAL_ATTRIBUTE_NAMES="..." java -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched: 1 java -jar build/libs/cas.war --cas.authn.surrogate.core.principal-attribute-names="..." The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.
  cas.authn.surrogate.core.principal-attribute-values= The regular expression that is cross matched against the principal attribute to determine if the account is authorized for impersonation. Matching and comparison operations are case insensitive. This settings supports regular expression patterns. [?]. org.apereo.cas.configuration.model.support.surrogate.SurrogateCoreAuthenticationProperties. How can I configure this property? CAS Property: cas.authn.surrogate.core.principal-attribute-values Configuration properties can be included and activated using the following strategies. 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. Java Property YAML Property System Property Environment Variable Command-line Argument CAS properties can be specified using the Java configuration property syntax in any and all .properties files: 1 cas.authn.surrogate.core.principal-attribute-values=... This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework. CAS properties can be specified using the YAML syntax: 1 cas: authn: surrogate: core: principal-attribute-values: "..." Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice. CAS properties can be passed to the CAS web application as system properties, when the application is launched: 1 java -Dcas.authn.surrogate.core.principal-attribute-values="..." -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as 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. CAS properties can specified as system environment variables before the CAS web application is launched: 1 2 3 export CAS_AUTHN_SURROGATE_CORE_PRINCIPAL_ATTRIBUTE_VALUES="..." java -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched: 1 java -jar build/libs/cas.war --cas.authn.surrogate.core.principal-attribute-values="..." The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.
  cas.authn.surrogate.core.separator=+ The separator character used to distinguish between the surrogate account and the admin/primary account. For example, if you are casuser and you need to switch to jsmith as the surrogate (impersonated) user, the username provided to CAS would be jsmith+casuser. org.apereo.cas.configuration.model.support.surrogate.SurrogateCoreAuthenticationProperties. How can I configure this property? CAS Property: cas.authn.surrogate.core.separator Configuration properties can be included and activated using the following strategies. 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. Java Property YAML Property System Property Environment Variable Command-line Argument CAS properties can be specified using the Java configuration property syntax in any and all .properties files: 1 cas.authn.surrogate.core.separator=+ This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework. CAS properties can be specified using the YAML syntax: 1 cas: authn: surrogate: core: separator: "+" Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice. CAS properties can be passed to the CAS web application as system properties, when the application is launched: 1 java -Dcas.authn.surrogate.core.separator="+" -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as 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. CAS properties can specified as system environment variables before the CAS web application is launched: 1 2 3 export CAS_AUTHN_SURROGATE_CORE_SEPARATOR="+" java -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched: 1 java -jar build/libs/cas.war --cas.authn.surrogate.core.separator="+" The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

  # Impersonation can be authorized for all primary users/subjects carrying specific attributes with a predefined matching value specified via {@link #principalAttributeValues}. # cas.authn.surrogate.core.principal-attribute-names= # The regular expression that is cross matched against the principal attribute to determine if the account is authorized for impersonation. # cas.authn.surrogate.core.principal-attribute-values= # The separator character used to distinguish between the surrogate account and the admin/primary account. # cas.authn.surrogate.core.separator=+

  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.

  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, 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.

  Usage Warning

  Be careful with this strategy! Once a match is found, CAS will completely back away from validating and verifying the requested surrogate account and the admin user is authorized to impersonate everyone and anyone.

• The underlying account store can mark a primary impersonator account with special permissions and privileges to allow it to impersonate any other account. Accounts that are whitelisted and wildcarded in this strategy are not assigned a specific list of authorized impersonatees but instead are able to impersonate any other username without any restrictions or additional checks.

  Usage Warning

  Be careful with this strategy! Designating an account as a wildcard will disable any and all other checks on the surrogate/impersonated account and CAS will completely back away from validating and verifying the requested surrogate account.

  To designate an account as a wildcard, the account store must be able to return and provide a list of authorized impersonated accounts for the primary user with * as the only entry in the list, indicating the primary user is authorized to impersonate anyone. Also, note that account selection using a GUI approach is disabled and turned off for wildcarded accounts. The primary user tagged as a wildcard must begin the impersonation flow using the Preselected approach with a known surrogate user.