Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 28435 invoked from network); 13 May 2003 15:19:35 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 13 May 2003 15:19:35 -0000 Received: (qmail 12942 invoked by uid 97); 13 May 2003 15:21:41 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 12935 invoked from network); 13 May 2003 15:21:41 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 13 May 2003 15:21:41 -0000 Received: (qmail 22370 invoked by uid 500); 13 May 2003 15:18:08 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 22311 invoked from network); 13 May 2003 15:18:07 -0000 Received: from mail0.mekon.com (213.210.17.10) by daedalus.apache.org with SMTP; 13 May 2003 15:18:07 -0000 Received: from ext-int.router.mekon.com (relay-0.mail.mekon.com [213.210.17.254]) by mail0.mekon.com (8.11.6/8.11.6) with ESMTP id h4DFCGW04019 for ; Tue, 13 May 2003 16:12:16 +0100 Subject: RE: Obtaining authenticate principal from HttpSession... Date: Tue, 13 May 2003 16:18:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Obtaining authenticate principal from HttpSession... Thread-Index: AcMYqlMyXoSvxIwETLWESL8v5DAhegACMbjQACkXckAAAHDhQAAAa02QAACpr8AAAE+asA== From: "Rob Tomlin" To: "Tomcat Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Does it just need to know that the user has been authenticated? The other application uses Request.getUserPrincipal(...) to determine the authenticated user, which is then used to determine access rights. In fact the other application is the Slide WebDAV servlet. If possible I want to keep the authentication mechanism the same for = Slide. I really am looking for a solution so that when Slide uses=20 Request.getUserPrincipal(...) the correct Principal is returned, hence = the subclassed HttpServletRequestWrapper. I think perhaps using an attribute on the HttpSession may be ok, but it seems a bit of a kludge... Cheers Rob Tomlin --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org