Enterprise Single Sign-On for All

Digest Authentication

Digest authentication is one of the agreed-upon methods CAS can use to negotiate credentials with a user’s web browser. This can be used to confirm the identity of a user before sending sensitive information. It applies a hash function to the username and password before sending them over the network. Technically, digest authentication is an application of MD5 cryptographic hashing with usage of nonce values to prevent replay attacks. It uses the HTTP protocol.

Support is enabled by including the following dependency in the WAR overlay:

1
2
3
4
5
<dependency>
  <groupId>org.apereo.cas</groupId>
  <artifactId>cas-server-support-digest-authentication</artifactId>
  <version>${cas.version}</version>
</dependency>

For additional information on how digest authentication works, please review this guide.

Configuration

To see the relevant list of CAS properties, please review this guide.

Credential Management

By default, CAS attempts to cross-check computed hash values against what the client reports in the authentication request. In order for this to succeed, CAS will need access to the data store where MD5 representations of credentials are kept. The store needs to keep the hash value at a minimum of course.

By default, CAS uses its properties file to house the hashed credentials. Real production-level deployments of this module will need to provide their own data store that provides a collection of hashed values as authenticating accounts.

Client Requests

The following snippets demonstrate how a given Java client may use CAS digest authentication, via Apache’s HttpClient library:

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
34
final HttpHost target = new HttpHost("localhost", 8080, "http");

final CredentialsProvider credsProvider = new BasicCredentialsProvider();
credsProvider.setCredentials(
        new AuthScope(target.getHostName(), target.getPort()),
        new UsernamePasswordCredentials("casuser", "Mellon"));
        
final CloseableHttpClient httpclient = HttpClients.custom()
        .setDefaultCredentialsProvider(credsProvider)
        .build();
        
try {
    HttpGet httpget = new HttpGet("http://localhost:8080/cas/login");
    
    // Create AuthCache instance
    final AuthCache authCache = new BasicAuthCache();
    
    // Generate DIGEST scheme object, initialize it and add it to the local auth cache
    final DigestScheme digestAuth = new DigestScheme();
    digestAuth.overrideParamter("realm", "CAS");
    authCache.put(target, digestAuth);

    // Add AuthCache to the execution context
    final HttpClientContext localContext = HttpClientContext.create();
    localContext.setAuthCache(authCache);

    System.out.println("Executing request " + httpget.getRequestLine() + " to target " + target);
    try (CloseableHttpResponse response = httpclient.execute(target, httpget, localContext)) {
        System.out.println(response.getStatusLine());
        System.out.println(EntityUtils.toString(response.getEntity()));
    }
} finally {
    httpclient.close();
}