Bottle CAS Bridge

Introduction

BottleCasBridge is Central Authentication Service (CAS) server that uses a SAML2 server perform the actual authentication function. BottleCasBridge is a Python application utilizing the Bottle Web framework

This bridge allows legacy CAS applications to utilize Identity Management platform that support SAML2 authentication. The difference between any other CAS server and the bridge is that the authentication dialog is handled by the SAML IdP.

The protocol flow thus combines both CAS and SAML:

• Client accesses a legacy CAS app, invoking a login.
• The app redirects the user to /cas/login on the BottleCasBridge
• If the client has not already authenticated with the bridge (i.e. has no Ticket Granting Ticket cookie), it is redirected to the SAML IdP login URL for authentication.
• The SAML IdP validates the user via dialog or SSO.
• The SAML Response is posted back (through the client) to the SAML assertion control service on the BottleCasBridge
• The signature on the SAML response is verified and the SAML assertions are saved in a session for the client.
• The client is then redirected back to the BottleCasBridge /cas/login
• The bridge returns a CAS Ticket Granting Ticket (TGT) as a cookie, and a Session Ticket back to the client with a redirect back to the legacy CAS application.
• The CAS application service validates the service ticket with the BottleCasBridge version specific cas endpoint.
• Depending on the CAS version configured and the API used the bridge returns the attributes for the user to the application.
• The client is then authenticated with the CAS application.

CAS Support

BottleCasBridge supports the CAS Protocol v1, v2, and v3 as defined by V2 of the CAS Specification with a few options not implemented.
These unemplemented features are lesser used items that did not fit within the SSO experience:

• gateway - section 2.1.1 #3 - the specification is unclear on the implementation, and the value of the feature I felt was suspect.
• logon credential receptor - section 2.2 - I don't belive this can be implemented with a SAML IdP.
• /cas/validate (the version 1 endpoint) returns the user login on a successful validation. Though not part of the CAS spec almost all CAS servers do this.

BottleCasBridge has been tested against Microsoft Azure AD and PHP SimpleSaml IdPs. If you use this with other IdPs I'd like to hear your experience.

Installation

It's recommended that you install BottleCasBridge in a venv. Some familiarity with Python apps is desirable.

# pip install BottleCasBridge

This will install Bottle, BottleCasBridge, BottleSessions, and BottleSaml and their dependencies.

There is a sample application app.py and a config_sample.py (for building your config.py) included with the distribution or available on github.

The basic structure of the CAS bridge is simple:

from bottle import Bottle
from BottleSessions import BottleSessions
from BottleSaml import SamlSP
from BottleCasBridge import CasBridge

from config import saml_config, session_config, cas_config

app = Bottle()

ses = BottleSession(app, session_config)
saml = SamlSP(app, ses, saml_config)
cas = CasBridge(app,auth=saml,config=cas_config, backing=ses.backing)

app.run()

The real work is in configuring the config.py components and the IdP to all work together.

Session and Ticket Configuration

BottleCasBridge uses BottleSessions (which in turn uses Pallets cachelib) to provide flexible configuration for both user sessions and ticket storage. This can include memory or filebased caching as well as Redis or memcached mechanism.

Details on configuring the cache is detailed in the BottleSessions documentation and the Pallets project cachelib documentation.

The simplist deployment suitable for testing is a memory based cache not requiring detailed options, however in a production deployment you will want to consider FileSystem, Memcached, or Redis as the cache backing.

SAML Configuration

You will need to configure the SamlSP module with details on the SAML IdP.

Some notes on SAML with BottleCasBridge:

• Uses the BottleSaml service provider implementation
• Does not sign SAML Requests, though it verifies the SAML signature on the SAML Response.
• Considers assertions received valid for 3600 Seconds from authentication regardless of CONDITIONS statements. (This is based on limitations of the minisaml implementation used.)
• Assertions are available in the v2/v3 CAS validation data.

Configue for your SAML IdP according to the documentation for BottleSaml This will include endpoints, entity id's, etc.

Configuring CAS

CasBridge(app, auth=saml, config=cas_config, backing=sess.backing)

• Note the Session backing is being used for the CasBridge ticket backing as well (backing=sess.backing). It is possible to use a different backing mechanism if desired (See Backing details for BottleSessions)

Cas config options

cas_config = {
    "cas_st_life" : 500,
    "cas_tgt_life" : 28800, 
    "cas_services_filename" : "/configs/cas_services.json",
    "cas_proxy_support" : True
}

cas_service_file and cas_proxy_file files

These are files with a JSON list of service/targetService) URL's from CAS applications that are permitted to use the CAS bridage. In the case of the cas_proxy_file these are acceptable pgtUrl for proxy validations.

URLs are checked with forced lower case matching. The URL from the request service parameter must start with one of the URLs in the list.

['https://example.com/app1', 'https://other.example.com/']

If cas_service_file or cas_proxy_files are not specified, CasBridge works as an open CAS server (unadvised) meaning any CAS app can use the bridge to authenticate (or proxy.)

Considerations for Production

• The default Bottle WSGI server is designed for development and maybe test, and is not suitable for production.
• The default memory-base BottleSession cache will not work in a multi-process environment. You can use FileSystem for a single-node solution, but will require memcached or Redis for multi-node solutions.
• Use TLS.
• If you do not have apps that require it, disable the proxy endpoints (cas_proxy_support=False).
• Restrict what services can use the bridge with the cas_service_file and cas_proxy_file settings.