[JBoss JIRA] Created: (JBWEB-66) basic-auth broken
by Mark Stewart (JIRA)
basic-auth broken
-----------------
Key: JBWEB-66
URL: http://jira.jboss.com/jira/browse/JBWEB-66
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBoss Web Server 1.0.0 GA
Environment: Linux
Reporter: Mark Stewart
Assigned To: Mladen Turk
Assuming that Jboss Web is configured identically to the web container in AS, it seems that basic-auth support is broken. That is, the server doesn't send a 401 for protected urls.
Here's the post I made three weeks ago on the Jboss Web Server forum:
"I have a webapp I usually run in JBoss AS that I'm trying to get running under JBossWeb. I've added the same entry to login-module.xml in the default/conf/ directory and a jboss-web.xml file whose <security-domain> tag points at the entry in default/deploy/<my-web-app.war>/WEB-INF. JBossWeb doesn't block the access to the protected pages, however."
This is tested by the J2EE CTS so I guess JBossWeb wasn't tested against it (or the failure was ignored) prior to the GA release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBAS-3426) Fix org.jboss.test.jacc.test.WebIntegrationUnitTestCase in HEAD
by Anil Saldhana (JIRA)
Fix org.jboss.test.jacc.test.WebIntegrationUnitTestCase in HEAD
---------------------------------------------------------------
Key: JBAS-3426
URL: http://jira.jboss.com/jira/browse/JBAS-3426
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security, Web (Tomcat) service
Environment: org.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC)
as well as org.jboss.test.jacc.test.WebIntegrationUnitTestCase
Reporter: Anil Saldhana
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta
There is privileges related exception that is showing up in HEAD whereas in Branch_4_0, does not show up.
=======================================================================================
10:37:07,843 INFO [ENCServlet] InitialContext.env:
10:37:07,843 INFO [ENCServlet] Key: java.naming.factory.initial, value: org.jnp.interfaces.NamingContextFactory
10:37:07,843 INFO [ENCServlet] Key: java.naming.factory.url.pkgs, value: org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
10:37:07,890 ERROR [[invoker]] Allocate exception for servlet invoker
java.lang.SecurityException: Servlet of class org.apache.catalina.servlets.Invok
erServlet is privileged and cannot be loaded by this web application
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1114)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:784)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
=========================================================================================
Something changed in TC6 as to how web apps can invoke the container servlets?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBCACHE-711) Replication eats out exception on the remote node
by Ben Wang (JIRA)
Replication eats out exception on the remote node
-------------------------------------------------
Key: JBCACHE-711
URL: http://jira.jboss.com/jira/browse/JBCACHE-711
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Replication
Affects Versions: 1.4.0
Reporter: Ben Wang
Assigned To: Manik Surtani
Fix For: 2.0.0
I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce.
21:51:32,490 INFO [TxInterceptor] There was a problem handling this request
java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable.
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114)
at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBREM-549) remove dependancy on concurrent.jar within remoting client
by Tom Elrod (JIRA)
remove dependancy on concurrent.jar within remoting client
----------------------------------------------------------
Key: JBREM-549
URL: http://jira.jboss.com/jira/browse/JBREM-549
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id. Problem is that org.jboss.util.id.GUID is what requires concurrent.jar. So will either need to modify the code within jboss common repository or find another class to use for generating the client session id.
java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong
at org.jboss.util.id.UID.<clinit>(UID.java:56)
at org.jboss.util.id.VMID.create(VMID.java:259)
at org.jboss.util.id.VMID.getInstance(VMID.java:223)
at org.jboss.util.id.GUID.<init>(GUID.java:65)
at org.jboss.remoting.Client.<init>(Client.java:133)
at org.jboss.remoting.Client.<init>(Client.java:210)
at org.jboss.remoting.Client.<init>(Client.java:191)
at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months