APEREO CASDocumentation

Enterprise Authentication for All Earthlings and Beyond

Identity, Single Sign-On and Access Management
View on GitHub

JWT Service Tickets

JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties. CAS may also be allowed to fully create signed/encrypted JWTs and pass them back to the application in form of service tickets.

JWTs are entirely self-contained and contain the authenticated principal as well as all authorized attributes in form of JWT claims.

:information_source: JCE Requirement

Make sure you have the proper JCE bundle installed in your Java environment that is used by CAS, specially if you need to use specific signing/encryption algorithms and methods. Be sure to pick the right version of the JCE for your Java version. Java versions can be detected via the java -version command.

Overview

JWT-based service tickets are issued to application based on the same semantics defined by the CAS Protocol. CAS having received an authentication request via its /login endpoint will conditionally issue back JWT service tickets to the application in form of a ticket parameter via the requested http method.

All JWTs are by default signed and encrypted by CAS based on keys generated and controlled during deployment. Such keys may be exchanged with client applications to unpack the JWT and access claims.

Flow Diagram

CAS Web flow JWT diagram

Note that per the above diagram, the JWT request by default internally causes CAS to generate an ST for the application and immediately then validate it in order to get access to the authenticated principal and attributes per policies associated with the application registration record in the CAS service registry. This response is transformed into a JWT that is then passed onto the client application.

In other words, the responsibility of receiving a service ticket (ST) and validating it is all moved into and handled internally by CAS. The application only needs to learn how to decipher and unpack the final JWT and ensure its validity.

The expiration time of the generated JWT is controlled by the length of the assertion returned as part of the validation event. If the assertion validity length is not specified, then the expiration time is controlled by the length of the SSO session defined as part of SSO expiration policy of the CAS server.

:warning: Not OpenID Connect

Remember that you are just receiving a ticket in form of a JWT, thereby removing the need from your client to validate a normal service ticket. The ticket is internally validated by CAS and you as the client are only left in charge of validating the JWT itself. Do not confuse this with OpenID Connect. While a JWT, the token itself is not an ID token, cannot be refreshed and must be obtained again once you deem it expired. If you need more, consider using the OpenID Connect protocol instead. Note that the responsibility of validating the JWT is pushed onto the client and NOT the CAS server itself.

Actuator Endpoints

The following endpoints are provided by CAS:

jwtTicketSigningPublicKey
CAS endpoint1 operationNot exposed by default
1

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.jwtTicketSigningPublicKey.access=UNRESTRICTED
management.endpoints.web.exposure.include=jwtTicketSigningPublicKey

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



1



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

Configuration

JWT support is enabled by including the following dependency in the WAR overlay:

Show in CAS Initializr Generate CAS Server WAR Overlay 


1
2
3
4
5



<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-token-tickets</artifactId>
    <version>${cas.version}</version>
</dependency>





1



implementation "org.apereo.cas:cas-server-support-token-tickets:${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-token-tickets"
}





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-token-tickets"
}

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

cas.authn.token.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.token.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.token.credential-criteriaA number of authentication handlers are allowed to determine whether they can operate on the provided credential and as such lend themselves to be tried and tested during the authentication handler selection phase.
no default
Regex
A number of authentication handlers are allowed to determine whether they can operate on the provided credential and as such lend themselves to be tried and tested during the authentication handler selection phase. The credential criteria may be one of the following options:
  • 1) A regular expression pattern that is tested against the credential identifier.
  • 2) A fully qualified class name of your own design that implements Predicate.
  • 3) Path to an external Groovy script that implements the same interface.
Type
String
Default
none
Defined by
TokenAuthenticationProperties
cas.authn.token.crypto.algThe signing/encryption algorithm to use.
no default

The signing/encryption algorithm to use.

Type
String
Default
none
Defined by
EncryptionOptionalSigningOptionalJwtCryptographyProperties
cas.authn.token.crypto.enabledWhether crypto operations are enabled.
true

Whether crypto operations are enabled.

Type
Boolean
Default
true
Defined by
EncryptionOptionalSigningOptionalJwtCryptographyProperties
cas.authn.token.crypto.encryption-enabledWhether crypto encryption operations are enabled.
true

Whether crypto encryption operations are enabled.

Type
Boolean
Default
true
Defined by
EncryptionOptionalSigningOptionalJwtCryptographyProperties
cas.authn.token.crypto.encryption.key-sizeThe encryption key size.
512

The encryption key size.

Type
Integer
Default
512
Defined by
EncryptionJwtCryptoProperties
cas.authn.token.crypto.signing-enabledWhether crypto signing operations are enabled.
true

Whether crypto signing operations are enabled.

Type
Boolean
Default
true
Defined by
EncryptionOptionalSigningOptionalJwtCryptographyProperties
cas.authn.token.crypto.signing.key-sizeThe signing key size.
512

The signing key size.

Type
Integer
Default
512
Defined by
SigningJwtCryptoProperties
cas.authn.token.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
EncryptionOptionalSigningOptionalJwtCryptographyProperties
cas.authn.token.nameName of the authentication handler.
no default

Name of the authentication handler.

Type
String
Default
none
Defined by
TokenAuthenticationProperties
cas.authn.token.orderOrder of the authentication handler in the chain.
no default

Order of the authentication handler in the chain.

Type
Integer
Default
none
Defined by
TokenAuthenticationProperties
cas.authn.token.sso-token-enabledWhen set to true, will generate a token and store it as an authentication attribute into the single sign-on session.
false

When set to true, will generate a token and store it as an authentication attribute into the single sign-on session. This token can be used later on for token-based authentication attempts, and should allow SSO access to the server.

Type
Boolean
Default
false
Defined by
TokenAuthenticationProperties
cas.authn.token.stateDefine the scope and state of this authentication handler and the lifecycle in which it can be invoked or activated.
active
Define the scope and state of this authentication handler and the lifecycle in which it can be invoked or activated. Available values are as follows:
  • ACTIVE: Active authentication handler, and is invoked by default automatically to verify credentials globally.
  • STANDBY: Authentication handler is in a semi-enabled state, waiting to be called only on-demand when explicitly asked for.
Type
AuthenticationHandlerStates
Default
active
Defined by
TokenAuthenticationProperties
cas.authn.token.webflow.enabledWhether webflow auto-configuration should be enabled.
true

Whether webflow auto-configuration should be enabled.

Type
Boolean
Default
true
Defined by
WebflowAutoConfigurationProperties
cas.authn.token.webflow.orderThe order in which the webflow is configured.
0

The order in which the webflow is configured.

Type
Integer
Default
0
Defined by
WebflowAutoConfigurationProperties

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.

RSA Keys

Certain CAS features such as the ability to produce JWTs as CAS tickets may allow you to use the RSA algorithm with public/private keypairs for signing and encryption. This behavior may prove useful generally in cases where the consumer of the CAS-encoded payload is an outsider and a client application that need not have access to the signing secrets directly and visibly and may only be given a half truth vis-a-vis a public key to verify the payload authenticity and decode it. This particular option makes little sense in situations where CAS itself is both a producer and a consumer of the payload.

:information_source: Remember

Signing and encryption options are not mutually exclusive. While it would be rather nonsensical, it is entirely possible for CAS to use AES keys for signing and RSA keys for encryption, or vice versa.

In order to enable RSA functionality for signing payloads, you will need to generate a private/public keypair via the following sample commands:



1
2



openssl genrsa -out private.key 2048
openssl rsa -pubout -in private.key -out public.key -inform PEM -outform DER

The private key path (i.e. file:///path/to/private.key) needs to be configured for the signing key in CAS properties for the relevant feature. The public key needs to be shared with client applications and consumers of the payload in order to validate the payload signature.

:information_source: Key Size

Remember that RSA key sizes are required to be at least 2048 and above. Smaller key sizes are not accepted by CAS and will cause runtime errors. Choose wisely.

In order to enable RSA functionality for encrypting payloads, you will need to essentially execute the reverse of the above operations. The client application will provide you with a public key which will be used to encrypt the payload and whose path (i.e. file:///path/to/public.key) needs to be configured for the encryption key in CAS properties for the relevant feature. Once the payload is submitted, the client should use its own private key to decode the payload and unpack it.

Authentication

Certain authentication handlers are allowed to determine whether they can operate on the provided credential and as such lend themselves to be tried and tested during the authentication handler selection phase. The credential criteria may be one of the following options:

  • A regular expression pattern that is tested against the credential identifier.
  • A fully qualified class name of your own design that looks similar to the below example:


1
2
3
4
5
6
7
8
9



import java.util.function.Predicate;
import org.apereo.cas.authentication.Credential;

public class PredicateExample implements Predicate<Credential> {
    @Override
    public boolean test(final Credential credential) {
        // Examine the credential and return true/false
    }
}
  • Path to an external Groovy script that looks similar to the below example:


1
2
3
4
5
6
7
8
9



import org.apereo.cas.authentication.Credential
import java.util.function.Predicate

class PredicateExample implements Predicate<Credential> {
    @Override
    boolean test(final Credential credential) {
        // test and return result
    }
}

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

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.

Register Clients

Signal the relevant application in CAS service registry to produce JWTs for service tickets:



1
2
3
4
5
6
7
8
9
10
11
12
13



{
  "@class" : "org.apereo.cas.services.CasRegisteredService",
  "serviceId" : "^https://.*",
  "name" : "Sample",
  "id" : 10,
  "properties" : {
    "@class" : "java.util.HashMap",
    "jwtAsServiceTicket" : {
      "@class" : "org.apereo.cas.services.DefaultRegisteredServiceProperty",
      "values" : [ "java.util.HashSet", [ "true" ] ]
    }
  }
}

Configure Keys Per Service

By default, the signing and encryption keys used to encode the JWT are global to the CAS server and can be defined via CAS settings. It is also possible to override the global keys on a per-service basis, allowing each application to use its own set of signing and encryption keys. To do so, configure the service definition in the registry to match the following:



1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25



{
  "@class" : "org.apereo.cas.services.CasRegisteredService",
  "serviceId" : "^https://.*",
  "name" : "Sample",
  "id" : 10,
  "properties" : {
    "@class" : "java.util.HashMap",
    "jwtAsServiceTicket" : {
      "@class" : "org.apereo.cas.services.DefaultRegisteredServiceProperty",
      "values" : [ "java.util.HashSet", [ "true" ] ]
    },
    "jwtAsServiceTicketSigningKey" : {
       "@class" : "org.apereo.cas.services.DefaultRegisteredServiceProperty",
       "values" : [ "java.util.HashSet", [ "..." ] ]
    },
    "jwtAsServiceTicketEncryptionKey" : {
         "@class" : "org.apereo.cas.services.DefaultRegisteredServiceProperty",
         "values" : [ "java.util.HashSet", [ "..." ] ]
    },
    "jwtAsServiceTicketCipherStrategyType" : {
         "@class" : "org.apereo.cas.services.DefaultRegisteredServiceProperty",
         "values" : [ "java.util.HashSet", [ "ENCRYPT_AND_SIGN" ] ]
    }
  }
}

The following cipher strategy types are available:

Type Description
ENCRYPT_AND_SIGN Default strategy; encrypt values, and then sign.
SIGN_AND_ENCRYPT Sign values, and then encrypt.

The following properties are available and recognized by CAS for various modules and features:

Name Default Value Type Group
jwtAsServiceTicket false BOOLEAN JWT_SERVICE_TICKETS
jwtAsServiceTicketCipherStrategyType ENCRYPT_AND_SIGN STRING JWT_SERVICE_TICKETS
jwtAsServiceTicketSigningKey STRING JWT_SERVICE_TICKETS
jwtAsServiceTicketEncryptionKey STRING JWT_SERVICE_TICKETS
jwtAsServiceTicketEncryptionAlg STRING JWT_SERVICE_TICKETS
jwtAsServiceTicketSigningEnabled true BOOLEAN JWT_SERVICE_TICKETS
jwtAsServiceTicketEncryptionEnabled true BOOLEAN JWT_SERVICE_TICKETS

JWT Validation - AES

The following example code snippet demonstrates how one might go about validating and parsing the CAS-produced JWT that is created using shared secrets via AES:



1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33



import org.apache.commons.codec.binary.Base64;
import org.jose4j.jwe.JsonWebEncryption;
import org.jose4j.jwk.JsonWebKey;
import org.jose4j.jws.JsonWebSignature;
import org.jose4j.keys.AesKey;

import java.nio.charset.StandardCharsets;
import java.security.Key;

...

var signingKey = "...";
var encryptionKey = "...";

var key = new AesKey(signingKey.getBytes(StandardCharsets.UTF_8));

var jws = new JsonWebSignature();
jws.setCompactSerialization(secureJwt);
jws.setKey(key);
if (!jws.verifySignature()) {
    throw new Exception("JWT verification failed");
}

var decodedBytes = Base64.decodeBase64(jws.getEncodedPayload().getBytes(StandardCharsets.UTF_8));
var decodedPayload = new String(decodedBytes, StandardCharsets.UTF_8);

var jwe = new JsonWebEncryption();
var jsonWebKey = JsonWebKey.Factory
    .newJwk("\n" + "{\"kty\":\"oct\",\n" + " \"k\":\"" + encryptionKey + "\"\n" + "}");

jwe.setCompactSerialization(decodedPayload);
jwe.setKey(new AesKey(jsonWebKey.getKey().getEncoded()));
IO.println(jwe.getPlaintextString());