> > Hi. > > On this list, it is preferred if you respond *below* the previous part. > It just makes it easier to follow the conversation later, for people who > search the archives. > > See : http://tomcat.apache.org/lists.html -> tomcat users -> important > > See below.
My bad. I'll be careful about that now :) > >> > You are not the only one. > Welcome to the delights of Windows Domain authentication. > > I do not know how Waffle works, but I would guess that the problemn is > that now Waffle tries to use your new Tomcat user-id, as the user-id under > which it "logs in" to the Domain, to authenticate /other/ web users. > And that user-id (the one which it now uses), does not have the correct > privileges to do this, /as a server/. > > Maybe you should consult the Waffle FAQ, to see if that kind of issue is > not already solved : > http://waffle.codeplex.com/wikipage?title=Frequently%20Asked%20Questions&referringTitle=Documentation > > I think that before that, you also have to decide between conflicting > scenarios : > - your webapp should authenticate to the external server with the same > user-id as the current authenticated webapp user > - your webapp should authenticate to the external server under the user-id > under which Tomcat runs as a Service > - your webapp should authenticate to the external server under some > arbitrary and fixed user-id from some configuration file (or web.xml of > your webapp). > > One last tip : generally-speaking, in any kind of Windows-Domain-based > authentication scenario, when a browser login dialog appears, it means that > the authentication has reverted to HTTP Basic authentication, and that is > usually a sign that something is not working as it should. > > I'll follow your suggestions and look at the Waffle FAQ. I have already read it to get Waffle working, but was'nt yet aware that it would prevent me from connecting to the external server. Between the conflicting scenarios, my choice would go to the third one (configuration file) or the first one if it's not possible. Thank you. Stéphane.
