Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311641 - no CallerPrincipalCallback returned misinterpreted as error
Summary: no CallerPrincipalCallback returned misinterpreted as error
Status: CLOSED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 8.0.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 7.0.2.RC0   Edit
Assignee: Greg Wilkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 18:51 EDT by David Jencks CLA
Modified: 2010-05-04 19:05 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Jencks CLA 2010-05-04 18:51:40 EDT 
the JaspiAuthenticator is interpreting not getting a CallerPrincipalCallback from the server auth context as an error.  However, it just means there is no authenticated user so Authentication.UNAUTHENTICATED should be returned.  For instance, if auth is not mandatory and you are not logged in, no CallerPrincipalCallback should be returned.

This applies to jetty 7 and jetty 8.
Comment 1 David Jencks CLA 2010-05-04 19:05:14 EDT 
Fixed jetty-8 rev 1704
jetty 7 (trunk) rev 1709