On Wed, Mar 30, 2011 at 01:35:09PM -0500, Scott T. Hildreth wrote: > On Wed, 2011-03-30 at 14:12 -0400, Kevin Falcone wrote: > > On Wed, Mar 30, 2011 at 12:15:10PM -0500, Scott T. Hildreth wrote: > > > I installed 4.0.0rc7 for testing. Our production version is 3.8.4. > > > The 3.8.4 install has "Set($WebExternalAuth , 1);" in the > > > RT_SiteConfig.pm and Apache2::AuthCAS set up in the Apache config. > > > This works in 3.8.4, but when I set it up for 4.0.0rc7 and tried to > > > login I was redirected to our CAS login page as expected and then > > > redirected back the RT login page that says the login failed and > > > has the login text box showing (which does not accept text). Is there > > > something more I need to do for 4.0 or did I forgot some setting? > > > > Does your apache log show that REMOTE_USER is being set to what you > > expect? > > I don't see REMOTE_USER in the logs, but I do see this > > CAS(95219): setHeader: Setting header: CAS_FILTER_USER = shildret
That isn't a header that RT matches on, did you have a local customization to 3.8.4 to handle that? -kevin > > There have been several changes since 3.8.4 for the login > > path, so you may be better off testing if 3.8.9 also fails for you. > > > > I know of a few folks using RT's External Auth against the 4.0.0 > > betas, so I suspect a misconfiguration or some weird bug we haven't > > seen yet, rather than a general failure.
pgpnEQGR2KDd2.pgp
Description: PGP signature
