Is anyone able to provide guidance on editing ood_portal.yml to support CAS authentication? I tried a few ideas that did not work, based on our implementation test outlined below – which provided a successful test.
We have implemented CAS through a download and build of mod_auth_cas from this repo: https://github.com/apereo/mod_auth_cas. The service was configured in the system, and then we made ad-hoc edits to the existing ood configuration in
/opt/rh/httpd24/root/etc/httpd/conf.d to verify that the service would recognize OoD.
This was realized through direct edit of the ood-portal.conf, and by creating a
cas.conf file in
In reviewing the differences between ood-portal.conf in the successful test case, and the ‘standard’ configuration, the meaningful differences are few:
< AuthType CAS
> AuthType Basic
< #AuthUserFile “/opt/rh/httpd24/root/etc/httpd/.htpasswd”
> AuthUserFile “/opt/rh/httpd24/root/etc/httpd/.htpasswd”
Only setting the VIrtualHost through ood_config.yml is unclear – the other two values are somewhat documented in the code. I tried to set the public IP using the ‘servername’ keyword, and then also ‘virtualhost’, and in both cases the result was ‘VIrtualHost *:80’