> From: André Warnier [mailto:[EMAIL PROTECTED]
> Subject: Re: HttpServletRequest.getUserPrincipal
>
> As for the 1.5 Java specs, there are indeed a couple of
> black holes in the "Principal" area.
I think you have to look at the security discussion in the spec in light
Caldarale, Charles R wrote:
From: André Warnier [mailto:[EMAIL PROTECTED]
Subject: Re: HttpServletRequest.getUserPrincipal
Sorry for not answering sooner
you are forgiven
- it's easier to do the source searching at home.
is getRemoteUser() merely a shortcut, under which
happ
> From: André Warnier [mailto:[EMAIL PROTECTED]
> Subject: Re: HttpServletRequest.getUserPrincipal
Sorry for not answering sooner - it's easier to do the source searching at home.
> is getRemoteUser() merely a shortcut, under which
> happens a getUserPrincipal.getName()
A
Caldarale, Charles R wrote:
From: André Warnier [mailto:[EMAIL PROTECTED]
Subject: HttpServletRequest.getUserPrincipal
To get the authenticated user-id from within a filter or a
servlet, one calls HttpServletRequest.getUserPrincipal.getName()
or HttpServletRequest.getRemoteUser()
Are these *
> From: André Warnier [mailto:[EMAIL PROTECTED]
> Subject: HttpServletRequest.getUserPrincipal
>
> To get the authenticated user-id from within a filter or a
> servlet, one calls HttpServletRequest.getUserPrincipal.getName()
or HttpServletRequest.getRemoteUser()
> But where and more mysteriously
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
> To get the authenticated user-id from within a filter or a servlet, one
> calls HttpServletRequest.getUserPrincipal.getName() e.g.
Technically, it's not the user id. It's just a name for the principal.
For most authentic
