If I use that Location parameter:
1) With remote-user-auth.py disabled:
- login never results in an actual login
2) With remote-user-auth.py enabled:
- trac header says "logged in as (null) "
We reconfigured SiteMinder to "protect" (i.e. require redirect to login) from
"/trac/login" to "/trac", and seems to "work"; i.e. I can now login and stay
logged in. However:
- Simply visiting /trac automatically redirects to the SiteMinder login
page. I don't really want this; I'd rather people only have to login if they
want to edit something in Trac (i.e. I want them to have to click the "Login"
link first)
- visiting /trac/login results in a "Authentication information not
available" error from Trac. (but I am, in fact, logged in)
On 8/5/2015 4:24 PM, Leho Kraav wrote:
> On 05.08.2015 23:15, RjOllos wrote:
>>
>> lkraav, who wrote the content on
>> the TracStandalone#Authenticationfortracdbehindaproxy page after getting
>> mod_proxy working with TracStandalone, suggested just changing the path
>> of the Location directive:
>>
>> <Location "/trac">
>> RequestHeader set REMOTE_USER %{REMOTE_USER}s
>> </Location>
> That I did. I'm running this with Apache mod_proxy + tracd. I'm not sure
> how this works out when there's a module trying to pass the header over
> to a Location block, but give it a shot and let us know.
>
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
