CASAuthNHeader bizzare behaviour

[Trenton D. Adams]

I added the following debug code...

  ap_log_error(APLOG_MARK, APLOG_ERR, 0, NULL,
    "MOD_AUTH_CAS: attempting to configure the header");
  c->CASAuthNHeader = (add->CASAuthNHeader != CAS_DEFAULT_AUTHN_HEADER ? add->CASAuthNHeader : base->CASAuthNHeader);
  ap_log_error(APLOG_MARK, APLOG_ERR, 0, NULL,
    "MOD_AUTH_CAS: configuration complete: %s-%s-%s-%s",
    c->CASAuthNHeader, add->CASAuthNHeader,
    CAS_DEFAULT_AUTHN_HEADER,base->CASAuthNHeader);

And hardcoded the default value to "x_cas_user".  And got...

[Tue Feb 12 10:17:45 2008] [error] MOD_AUTH_CAS: attempting to configure the header
[Tue Feb 12 10:17:45 2008] [error] MOD_AUTH_CAS: configuration complete: on-on-x_cas_user-x_cas_user
[Tue Feb 12 10:17:45 2008] [error] MOD_AUTH_CAS: attempting to configure the header
[Tue Feb 12 10:17:45 2008] [error] MOD_AUTH_CAS: configuration complete: on-on-x_cas_user-x_cas_user

In other words, the header configuration seems to be working just fine.  But, the question is why doesn't it work.

I noticed that setting any of the directives that are declared in cas_cmds as using "ap_set_string_slot" have the exact same behaviour.  i.e. they mess up the redirect, and send it to login.example.com.

----- "Trenton D. Adams" <trenta at athabascau.ca> wrote:
> Hi Matt,
> 
> Okay, where do I file bug reports?  It definitely happens with 1.0.6
> as well.
> 
> ----- "Matt Smith" <matt.smith at uconn.edu> wrote:
> > Trenton-
> > 
> >   For now, don't use the 1.0.7 series ... there is a content-eating
> > bug introduced by trying to handle the SAML Logout POST.
> >   If this happens with 1.0.6, please file a bug report.  This
> feature
> > has not been thoroughly exercised, so they may still be some
> > wrinkles.
> > 
> > Thanks,
> > -Matt
> > 
> > -----Original Message-----
> > From: cas-bounces at tp.its.yale.edu on behalf of Trenton D. Adams
> > Sent: Mon 2008-02-11 17:40
> > To: Yale CAS mailing list
> > Subject: CASAuthNHeader bizzare behaviour
> >  
> > Hi Guys,
> > 
> > I'm trying to use the special user header feature of mod_auth_cas,
> and
> > I'm getting extremely odd behaviour.  Whenever I try to set it, I
> get
> > redirected to login.example.com....., which is the default login
> site
> > if you haven't configured one.  When I comment out the
> CASAuthNHeader
> > line, everything works just fine.
> > 
> > I took a quick look at the code, and I couldn't see anything
> obviously
> > wrong.
> > 
> > I'm using RC2 of 1.0.7 
> > 
> > Any ideas?
> > 
> > __ 
> >     This communication is intended for the use of the recipient to
> > whom it
> >     is addressed, and may contain confidential, personal, and or
> > privileged
> >     information. Please contact us immediately if you are not the
> > intended
> >     recipient of this communication, and do not copy, distribute,
> or
> > take
> >     action relying on it. Any communications received in error, or
> >     subsequent reply, should be deleted or destroyed.
> > ---
> > _______________________________________________
> > Yale CAS mailing list
> > cas at tp.its.yale.edu
> > http://tp.its.yale.edu/mailman/listinfo/cas
> > 
> > _______________________________________________
> > Yale CAS mailing list
> > cas at tp.its.yale.edu
> > http://tp.its.yale.edu/mailman/listinfo/cas
> 
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas