tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: Do any of the Tomcat LDAP-type realms support "no password" authentication?
Date Sat, 03 Dec 2011 15:15:07 GMT wrote:
> ---- wrote: 
>> ---- "André Warnier" <> wrote: 
>>> wrote:
>>>> ---- "André Warnier" <> wrote: 
>>>>> wrote:
>>>>> .. re-synchronising..
>>>>>> I've made some progress.  I have a VirtualHost, so I had to add a
"JkMountCopy 'on'" inside the <VirtualHost>, and now, it's at least proxying through
to the Tomcat using mod_jk!!
>>>>>> BUT, it's still not logging me into the Tomcat :(...
>>>>>> I don't want to post the entire jk.log, so can someone point me to
what to look for in there, maybe?
>>>>> Ok, so let's now continue on the mod_jk track, since you've got that
part running.
>>>>> What you are looking for, is an AJP "request attribute" named "remote_user"
>>>>> in the packets which mod_jk sends to Tomcat.
>>>>> I don't know if that would be in the log, nor if there is any way to
coerce mod_jk into 
>>>>> putting it in the log.
>>>>> But since your Tomcat is not authenticating, chances are that it isn't
>>>>> So let's try to cheat, and force it to be there.
>>>>> In your Apache configuration, add this line :
>>>>> JkEnvVar remote_user "blablabla"
>>>>> and let's see what happens.
>>>>> (and after that, we'll try mod_rewrite or a combination)
>>>> Andre,
>>>> I had already tried including a "JkEnvVar" as you suggested in my httpd.conf,
in order to try to hard-code getting SOMETHING  to show up, but no joy :(...
>>>> I've also tried a bunch of other variants:
>>>> JkEnvVar  REMOTE_USER
>>>> also:
>>>> JkEnvVar remote_user "foobar"
>>>> also:
>>>> JkEnvVar AJP_REMOTE_USER "foobar"
>>>> Nothing works :(...
>>>> This is really getting discouraging :(.  It almost seems to me like that
'tomcatAuthentication' functionality doesn't even exist at all.
>>>> I've searched the jk.log for multiple things, "attr", "remo", etc., and find
nothing relevant/significant at all in there...
>>> Do not get discouraged.  I can guarantee that the tomcatAuthentication="false"
works, when 
>>> the Apache front-end really does authenticate the user.  I use this all the time.
>>> (Just not with the same SSO mechanism as you).
>>> I also know that "JkEnvVar" does work in general for setting request attributes
at the 
>>> Apache level, and have them passed to Tomcat by mod_jk, because I also us that
>>> (And there exists a similar functionality in mod_proxy_ajp).
>>> What may not work in the trials above, is that specifically this "remote_user"
>>> attribute may be overwritten by mod_jk or mod_proxy_ajp, even when you have set
>>> explicitly in Apache.
>>> After all, this feature is designed to do one thing : examine the "request record"
>>> Apache for an authenticated user-id, and if one is set, pass it along to Tomcat
over the 
>>> AJP channel.  If mod_jk/mod_proxy_ajp do not find such a user-id in the request
>>> they may just /clear/ the remote_user attribute, thus voiding our attempts at
>>> To verify this is relatively simple.
>>> Create the following <Location> section in Apache :
>>> <Location /sampleajp>
>>>    AuthType Basic
>>>    AuthName "toTomcat"
>>>    AuthUserFile /some-path/passwords
>>>    Require user testuser
>>>    SetHandler jakarta-servlet
>>>    SetEnv JK_WORKER_NAME tomcatA   (<- or whatever name your worker has)
>>> <Location>
>>> Note: the SetHandler and SetEnv lines above, in that <Location>, are equivalent
to saying :
>>>    JkMount /sampleajp/* tomcatA
>>> Then follow the instructions here to create the password file and the user "testuser"
in it :
>>> section : Getting it working
>>> If you try to access such a URL "/sampleajp/*", the browser will popup a bssic
auth dialog 
>>> and force you to login.
>>> This will result in the request being duly authenticated for Apache, which /will/
>>> in the Apache user-id being passed to Tomcat.
>>> Then, once you have verified (in Tomcat) that it is so, have another look at
the mod_jk 
>>> logfile, to see if then you spot the attribute being passed.
>>> (You will know that it is passed, but it may still not show up the logs).
>>> If all of that works, then we know that in order for your scheme to work, you
must somehow 
>>> force the user-id obtained by your SSO system, to be also set in the Apache request

>>> record.  Which should be a solvable problem.
>>> And if not, then you still have your Valve..
>> Andre,
>> I haven't tried your full suggestion yet, but I removed all of the OAM SSO stuff
out of my Apache httpd.conf, just to see what happens, but even after that, still am not getting
logged into Tomcat, so it may be as you suggest, that mod_jk tries to get the userid from
somewhere deep inside of Apache.
>> So, I will try adding what you suggested, to get authenticated with just the Apache,
and then see what happens, and will post back.  If that works, we can go from there.
>> Thanks for following up with this!
>> Jim
> Hi Andre,
> I configured the <Location> as you suggested, and guess what?
> That was good, BUT, recall that I had removed the OAM stuff from the Apache .conf earlier.
> So, after confirming that, without the OAM stuff, and with your suggested <Location>,
that it worked, I then went and uncommented the OAM stuff, i.e., added back the OAM agent.

Well, you should have one OR the other, not both.
Comment-out the Basic authentication stuff, as below, and /then/ add your OAM stuff inside

the location instead.

<Location /sampleajp>
# AuthType Basic
# AuthName "toTomcat"
# AuthUserFile /some-path/passwords
# Require user testuser

# leave these as they are :
     SetHandler jakarta-servlet
     SetEnv JK_WORKER_NAME tomcatA   (<- or whatever name your worker has)

# add the OAM stuff here :


(and show us an example of the OAM setup , passwords etc. removed of course)
(Maybe also, if you have a pointer to some documentation explaining the OAM setup, that 
may be helpful too).

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message