tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Nybro Bolding" <thomas.bold...@danskebank.dk>
Subject Vedr.: IIS and Tomcat security
Date Fri, 16 Apr 2004 07:28:38 GMT
Yes it does.

request.getRemoteUser() in your JSP gives you the IIS authenticated user. Make sure your IIS
is set to Integrated Windows authentication and insert request.tomcatAuthentication=false
in your jk2.properties file.

/Thomas





"Insyde" <insyde@insyde.com.br>
15-04-2004 18:06
Besvar venligst til "Tomcat Users List"

 
        Til:    <tomcat-user@jakarta.apache.org>
        cc: 
        Vedr.:  IIS and Tomcat security



Hi

Does JK2 connector pass a security information to Tomcat, like the 
authenticated user? I coudn't find any information about this in JK2 
documentation. In my project, I need that the IIS authenticates the users, and then, the Tomcat
executes my web application with users and roles 
information.

Thanks

Maurício Kanada



<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>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message