I don’t have experience with CAS, but I’ve definitely used Keycloak for OpenID Connect and SAML 2.

It actually looks like there is an unofficial CAS extension for Keycloak too: https://github.com/jacekkow/keycloak-protocol-cas.

This is the Docker image I usually use for testing: https://hub.docker.com/r/jboss/keycloak/.

David Cook

Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

Office: 02 9212 0899

Online: 02 8005 0595

From: Tomas Cohen Arazi <tomascohen@theke.io>
Sent: Wednesday, 17 March 2021 11:41 AM
To: David Cook <dcook@prosentient.com.au>
Cc: koha-devel <koha-devel@lists.koha-community.org>; Renvoize, Martin <martin.renvoize@ptfs-europe.com>
Subject: Re: Automated testing Koha-Shibboleth integration

it would be cool to have keycloak server to aid testers. This way CAS and Shibb bugs would move faster.

El mar., 16 mar. 2021 21:26, <dcook@prosentient.com.au> escribió:

Hi all,

Jonathan’s comment about the possibility of a Koha-Shibboleth regression got me thinking (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27555#c3). When we do releases, are we testing the Koha-Shibboleth integration?

I have some custom Shibboleth code for Koha, and when I’m testing it I use Keycloak (manually not automatically). I wonder if the community should run a Keycloak node for testing Koha’s Shibboleth integration.

I’m curious what people think.

David Cook

Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

Office: 02 9212 0899

Online: 02 8005 0595