The mailing list for listmasters using Sympa

[Olivier Salaün <address@concealed>]

Hello Christian,

I suppose that you wish to have Shibboleth authentication enabled on all 
your Sympa robots.
Then configuring the generic_sso parameters on the default auth.conf is 
enough to have applied to all virtual robots. The piece of log that you 
provide tells me that authentication does use sso_login(), which is a 
good sign.

The errror message you get "no REMOTE_USER HTTP header set" could 
reflect an issue in the Apache configuration. You should make sure that 
Shibboleth authentication is activated on all your Apache virtual hosts.

Just in case you missed it, here is the Shibb+Sympa documentation : 
<http://www.sympa.org/manual/authentication#setting_up_a_shibboleth-enabled_sympa_server>

If you need further help, you should provide more informations on your 
setup (auth.conf file + Apache configuration).

Le 04/05/2010 22:25, Christian Dahlhausen a écrit :
> I have set up Sympa 5.3.4. with Shibboleth 1.3 on a Ubuntu 8.04LTS. 
> Shibboleth and Sympa should be configured correctly since I can log in 
> on the main Sympa robot. However I cannot login in other robots on the 
> same machine.
> May  4 16:17:42 hops wwsympa[21738]: [robot xyz] [client 
> 111.222.333.444 ] main::do_sso_login() do_sso_login: user could not be 
> identified, no REMOTE_USER HTTP header set
>
> Does anybody have a similar setting or ran in a similar problem?