OpenID Connect - Identity Assurance

Identity Assurance defines an extension to OpenID Connect for providing Relying Parties with verified claims, along with an explicit statement about the verification status of these claims (what, how, when, according to what rules, using what evidence). This specification is aimed at enabling use cases requiring strong assurance, for example, to comply with regulatory requirements such as Anti-Money Laundering laws or access to health data, risk mitigation, or fraud prevention.

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

cas.authn.oidc.identity-assurance.verification-source.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 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.

org.apereo.cas.configuration.model.SpringResourceProperties.

_{How can I configure this property?}

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.

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.authn.oidc.identity-assurance.verification-source.location=...

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:

cas: 
  authn: 
    oidc: 
      identity-assurance: 
        verification-source: 
          location: "..."

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:

java -Dcas.authn.oidc.identity-assurance.verification-source.location="..." -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:

export CAS_AUTHN_OIDC_IDENTITY_ASSURANCE_VERIFICATION_SOURCE_LOCATION="..."

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:

java -jar build/libs/cas.war --cas.authn.oidc.identity-assurance.verification-source.location="..."

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.

_{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.}

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

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.

Identity Assurance Claims

CAS provides a special pre-defined built-in scope, assurance that carries special identity assurance claims. In order to fulfill the requirements of some jurisdictions on identity assurance, identity assurance defines the specific claims for conveying end-user data in addition to the Claims defined in the OpenID Connect specification. Such claims include nationalities, birth_family_name, birth_given_name, msisdn, place_of_birth and more.

Allow a relying party to receive claims grouped by the assurance scope may be done as follows:

{
  "@class" : "org.apereo.cas.services.OidcRegisteredService",
  "clientId": "...",
  "clientSecret": "...",
  "serviceId" : "...",
  "name": "OIDC",
  "id": 1,
  "scopes" : [ "java.util.HashSet", 
    [ "openid", "profile", "assurance" ]
  ]
}

Identity Assurance Audits

ID tokens generated by CAS carry a special txn claim used in the context of identity assurance to build audit trails across the parties involved in an OpenID Connect transaction. CAS audit records maintain a corresponding audit trail tied to the txn claim which at least consists of the following details:

The transaction ID under txn
The authentication method employed under authn_methods
The generated ID token itself

ID Token

The generated ID token that shows up in the CAS audit logs is NOT unpacked to display and/or log claims in plain-text mode. The ID token is displayed as-is, and may be signed and or encrypted depending on the relying party configuration.

Identity Assurance Verifications

Identity assurance verification records are by default loaded from a JSON file whose path is taught to CAS via configuration properties. The file may contain multiple verification records:

[
    {
        "trust_framework": "eidas",
        "assurance_level": "substantial"
    },
    {
        "trust_framework": "it_spid",
        "time": "2019-04-20T20:16Z",
        "verification_process": "b54c6f-6d3f-4ec5-973e-b0d8506f3bc7",
        "evidence": [
            {
              "type": "document",
              "validation_method": {
                "type": "vcrypt"
              },
              "verification_method": {
                  "type": "bvr"
              },
              "time": "2019-04-20T20:11Z",
              "document_details": {
                "type": "passport",
                "issuer": {
                  "name": "Ministro Affari Esteri",
                  "country": "ITA"
                },
                "document_number": "83774554",
                "date_of_issuance": "2011-04-20",
                "date_of_expiry": "2021-04-19"
              }
            }
        ]
    }
]

Claim or attribute definitions that are marked as verifiable and are assigned a trust framework will receive special treatment when ID tokens or user profile payloads are generated. A rough outline of the verified claims in the final payload might be:

{
  "verified_claims": {
    "verification": {
      "trust_framework": "eidas",
      "assurance_level": "substantial"
    },
    "claims": {
      "given_name": "Max",
      "family_name": "Meier",
      "birthdate": "1956-01-28"
    }
  }
}

Custom

If you wish to design your own source of identity assurance verifications, you may plug in a custom implementation of the AssuranceVerificationSource that allows you to handle this on on your own:

@Bean
public AssuranceVerificationSource assuranceVerificationSource() {
    return new MyAssuranceVerificationSource();
}

See this guide to learn more about how to register configurations into the CAS runtime.