Hi,

just got started with CAS and got a segfault with mod_auth_cas. In order to 
reproduce this, this is what I've done:
* configured JDBC access in cas-server-webapp (3.3.1) as described in 
http://www.ja-sig.org/wiki/display/CASUM/Using+JDBC+for+Authentication. The cas 
server has IP 172.16.127.1
* set up a virtual machine running Debian Etch and compiled mod_auth_cas 
(1.0.8). This machine has IP 172.16.127.130
* the apache config (relevant snippets) looks like this:

LoadModule auth_cas_module /usr/lib/apache2/modules/mod_auth_cas.so

<IfModule mod_auth_cas.c>
        CASCookiePath /var/run/cas/
        CASLoginURL http://172.16.127.1:8081/cas-server-webapp/login
        CASDebug On
        CASValidateServer Off
</IfModule>

<VirtualHost *>
        ServerAdmin webmas...@localhost
        ServerName 172.16.127.130
        DocumentRoot /var/www/
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

<Directory "/var/www/protected">
    AuthType CAS
    Require valid-user
</Directory>

When trying to access http://172.16.127.130/protected, I get redirected to CAS 
login. After entering the login/pw I get redirected back to apache and get am 
empty page and the following error message in /var/log/apache2/error.log:
child pid 22560 exit signal Segmentation fault (11)

Any hints on this? For the test setup I did not use any SSL stuff, might this 
be the cause for the segfault?

Thanks,
Stefan

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to