Hey,
what I described yesterday was crap. The exceptions were not root of the
problem, they happen with 4.0.3, too (TRACE).
The problem happens due to the new tomcat way of authorization in
public class JBossSecurityMgrRealm extends RealmBase implements Realm
| ...
| public boolean
copy (not move) tomcat55-service.jar from deploy/jbossweb-tomcat to
server/default/lib
perhaps someone has a better solution?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3989605#3989605
Reply to the post :
Hello,
I've been playing around with the NegotiateLoginModule as it's described in the
Wiki. What I found out and found worthy to tell, I added in the Wiki Page (like
I promised to Anil in Berlin :).
Is anybody else working on / playing with that? Will it make its way into a GA
release one
If you want to see that authentication works just comment the authorization
stuff in getRoleSet and try it with sth like this instead:
anonymous wrote :
| Group curGroup = new SimpleGroup(authenticated);
| curGroup.addMember(ntlmIdent);
| roleGroup.addMember(curGroup);
|
I did not
I just faced the same problem, after updating to 4.0.5 from 4.0.3sp1.
It seems that BASIC authentication has been changed so that the prompt now is
triggered after the error page, i.e. when an error page is configured there is
no prompt anymore..
(I assume your 404 error code was due to not
