Hi Björn, I am using IIS 5.0 and JK2, dunno which version though. As in your setup users are authenticated by IIS and the credentials are passed to Tomcat. Since upgrading from JK I have experienced no problems so I assume its NOT a JK2 issue.
Cant tell whats wrong but be sure to add "request.tomcatAuthentication=false" to the jk2.properties file. /Thomas [EMAIL PROTECTED] 08-03-2004 13:23 Besvar venligst til "Tomcat Users List" Til: [EMAIL PROTECTED] cc: Vedr.: JK contra JK2 with IIS-Authentification Hi Group, We used JK 1.2.5 isapi-redirector in our IIS. The IIS authenticates the Users against the domain, and many applications take this info from request.getremoteuser and work with it. With JK2, this doesn't work any more. There is no Username passed to Tomcat. Why? Or anybody knows a workaround? Thanx for your braintime.. -- Björn Andersen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <FONT SIZE=1 FACE="Arial">_______________ Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selv om e-mailen og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge e-mailen. _______________ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. </FONT>