a lot.
-Mensaje original-
De: Jan Bartel [mailto:[EMAIL PROTECTED]]
Enviado el: viernes, 22 de marzo de 2002 10:36
Para: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Asunto: Re: [jetty-discuss] [Fwd: [JBoss-dev] Authentication with Jetty]
OK chaps, I'm going to have a shot at providing
I'm not following what you meant in your original post about
I get an exception one of each 3 times...
Hit refresh - ok
Hit refresh - ok
Hit refresh - Error 500
The error is thrown on any non-authenticated browser when there is an
authenticated one open. If you don't authenticate anyone (if
I'm not following what you meant in your original post about
I get an exception one of each 3 times...
Hit refresh - ok
Hit refresh - ok
Hit refresh - Error 500
The error is thrown on any non-authenticated browser when there is an
authenticated one open. If you don't authenticate
OK chaps, I'm going to have a shot at providing a solution to this.
I think what is happening is that Jetty is only setting the Principal
to null after it is finished handling a request, rather than both the
Principal *and* the Credential. Therefore, when no user has been
authenticated, both
- Original Message -
From: Jan Bartel [EMAIL PROTECTED]
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Friday, March 22, 2002 2:36 AM
Subject: Re: [jetty-discuss] [Fwd: [JBoss-dev] Authentication with Jetty]
OK chaps, I'm going to have a shot at providing a solution to this.
I think what
I tested it and it seems to work well by now with my app.
Thanks for the quick fix
/lothar
On Thu, 21 Mar 2002, Jan Bartel wrote:
I have checked in a fix for this problem, but I am afraid I am unable to
test the fix at the moment. Could someone retest and let me know if the
fix is solid?
I have checked in a fix for this problem, but I am afraid I am unable to
test the fix at the moment. Could someone retest and let me know if the
fix is solid?
You will need to update
$JBOSSHOME/jetty/src/main/org/jboss/jetty/security/JBossSecurityRealm.java
Thanks
Jan
Hi,
I noticed a
Ignacio,
(I'm cross posting this to jboss-dev and jetty-discuss)
I think your current problem has in fact always been a problem with
your webapp, but it has just been unmasked by a modification to the
thread authentication stuff we did recently. What we did was to ensure
that when a
Just to back up what Jan said
If you want to access beans that have security constraints, then
currently the URL must be one that has an authentication-constraint
specified.
The happenstance that a browser is actually sending basic authentication
information to a non-authenticated URL is
Hi Jan :)
(I'm cross posting this to jboss-dev and jetty-discuss)
I think your current problem has in fact always been a problem with
your webapp, but it has just been unmasked by a modification to the
thread authentication stuff we did recently. What we did was to ensure
that when a
Just to back up what Jan said
If you want to access beans that have security constraints, then
currently the URL must be one that has an authentication-constraint
specified.
The happenstance that a browser is actually sending basic authentication
information to a non-authenticated URL
- Original Message -
From: Ignacio Coloma [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, March 21, 2002 5:01 PM
Subject: RE: [jetty-discuss] [Fwd: [JBoss-dev] Authentication with Jetty]
Just to back up what Jan said
If you want
12 matches
Mail list logo
