On 24 January 2017 at 16:19, Chris Cheltenham <[email protected]> wrote: > Bryon , > > According to my tcpdump mod_auth_cas is pushing REMOTE_USER no matter what we > configure it to be. > So when we changed the behavior of the other side to EXPECT the REMOTE_USER > variable , it worked. > > The question for CAS folks is, Is that a bug? > > Is it supposed to ignore the configured value in our mod_auth_cas.conf file? > > I would think not.
mod_auth_cas sets r->user which gets evaluated as REMOTE_USER. This is something that can't be changed. What does your configuration look like? -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAAgu-wAtN3yqF_NaCYBF-JydjVc3JH05Y9U6QXQ_5kV5OrrQRQ%40mail.gmail.com.
