Groovy Attribute Resolution

The following configuration describes how to fetch and retrieve attributes from Groovy attribute repositories.

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

cas.authn.attribute-repository.groovy[0].locationThe location of the resource.

no default

Required

The location of the resource. Resources can be URLs, or files found either on the classpath or outside somewhere in the file system.

In the event the configured resource is a Groovy script, especially if the script is set to reload on changes, you may need to adjust the total number of inotify instances. On Linux, you may need to add the following line to /etc/sysctl.conf: fs.inotify.max_user_instances = 256.

You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.

In situations and scenarios where CAS is able to automatically watch the underlying resource for changes and detect updates and modifications dynamically, you may be able to specify the following setting as either an environment variable or system property with a value of false to disable the resource watcher: org.apereo.cas.util.io.PathWatcherService.

Type: Resource
Default: none
Defined by: GroovyPrincipalAttributesProperties

cas.authn.attribute-repository.groovyRetrieve attributes from multiple Groovy scripts.

no default

Retrieve attributes from multiple Groovy scripts.

Type: List<GroovyPrincipalAttributesProperties>
Default: none
Defined by: PrincipalAttributesProperties

cas.authn.attribute-repository.groovy[0].idA value can be assigned to this field to uniquely identify this resolver.

no default

A value can be assigned to this field to uniquely identify this resolver.

Type: String
Default: none
Defined by: GroovyPrincipalAttributesProperties

cas.authn.attribute-repository.groovy[0].orderThe order of this attribute repository in the chain of repositories.

no default

The order of this attribute repository in the chain of repositories. Can be used to explicitly position this source in chain and affects merging strategies.

Type: int
Default: none
Defined by: GroovyPrincipalAttributesProperties

cas.authn.attribute-repository.groovy[0].stateWhether attribute resolution based on this source is enabled.

ACTIVE

Whether attribute resolution based on this source is enabled. Available values are as follows:

ACTIVE: Active and enabled repository, and is invoked by default automatically.
DISABLED: Attribute repository is disabled and will not be used to resolve people and attributes.
STANDBY: Repository is in a semi-enabled state, waiting to be called only on-demand when explicitly asked for and will not be registered into the resolution plan.

Type: AttributeRepositoryStates
Default: ACTIVE
Defined by: GroovyPrincipalAttributesProperties

Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.

Groovy scripting

CAS takes advantage of Apache Groovy in forms of either embedded or external scripts that allow one to, by default, dynamically build constructs, attributes, access strategies and a lot more. To activate the functionality described here, you may need to prepare CAS to support and integrate with Apache Groovy.

Please review this guide to configure your build.

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.

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.

The Groovy script may be designed as:

import java.util.*

def run(final Object... args) {
    def (username,attributes,logger,properties,appContext) = args
    logger.debug("[{}]: The received uid is [{}]", this.class.simpleName, username)
    
    // All attribute values must be defined as a collection wrapped in []
    return [username:[username], likes:["cheese", "food"], id:[1234,2,3,4,5], another:["attribute"] ]
}

The following parameters are passed to the script:

Parameter	Description
`username`	Current principal identifier found from the authentication phase.
`attributes`	`Map` of query attributes built by CAS to construct the attribute resolution query.
`logger`	The object responsible for issuing log messages such as `logger.info(...)`.
`properties`	CAS configuration properties.
`appContext`	The current and active application context under the type `ApplicationContext`.

To prepare CAS to support and integrate with Apache Groovy, please review this guide.