Stef�n F. Stef�nsson wrote:
> woops... this bug should not have that severity or priority... I didn't
> notice any place where I should have set that now that I think of it...
> hmmm... weird... maybe it's a bug in the bug-tracking system?
>
Yah, it is ...
In response to the issue raised however, I should point out that Tomcat 3.2 does
not currently support the CLIENT-CERT mechanism for populating
request.getUserPrincipal(), and also for tying in to security constraints.
(Tomcat 4.0 does this.)
Craig McClanahan
>
> -----Original Message-----
> From: BugRat Mail System [mailto:[EMAIL PROTECTED]]
> Sent: 4. desember 2000 15:12
> To: [EMAIL PROTECTED]
> Subject: BugRat Report #516 has been filed.
>
> Bug report #516 has just been filed.
>
> You can view the report at the following URL:
>
> <http://znutar.cortexity.com/BugRatViewer/ShowReport/516>
>
> REPORT #516 Details.
>
> Project: Tomcat
> Category: Bug Report
> SubCategory: New Bug Report
> Class: swbug
> State: received
> Priority: high
> Severity: critical
> Confidence: public
> Environment:
> Release: 3.2
> JVM Release: 1.3
> Operating System: Windows 2000
> OS Release: 5.00.2195 w/SP1
> Platform: Intel x86
>
> Synopsis:
> request.getUserPrincipal() doesn't work when user is authenticated with
> a X509 client certificate.
>
> Description:
> Shouldn't this method return the subject DN of the clients X509
> certificate?
