[JBoss JIRA] (WFLY-6004) JAASCallbackHandler resets SecurityContext after authentication to it's pre-authentication value
by Ian MacIntyre (JIRA)
Ian MacIntyre created WFLY-6004:
-----------------------------------
Summary: JAASCallbackHandler resets SecurityContext after authentication to it's pre-authentication value
Key: WFLY-6004
URL: https://issues.jboss.org/browse/WFLY-6004
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.CR5, 9.0.2.Final
Reporter: Ian MacIntyre
Assignee: Jason Greene
We are using remote EJB calls and are finding role information being lost.
I have traced this to our use of JAAS authentication for the ApplicationRealm security realm
Within the handle() method of JaasCallbackHander it stores the current Security context at that point (via securityManager.push())
It then calls securityManager.authenticate() which results in login modules being called. We use the ClientLoginModule which stores information on the SecurityContext via SecurityAssociationActions.setPrincipalInfo
After authentication the JaasCallbackHandler calls securityManager.pop() which resets the SecurityContext back its state before authentication - thus losing the context set in the ClientLoginModule.
This only occurs via a remote ejb call, not via a call made from the web tier (as it does not use JaasLoginHandler)
Ideally I'd like some way to stop the JaasCallbackHandler reseting the SecurityContext (even if it was incredibly simple by checking for an attribute on the current security context)
The same operations work in EAP 6.3 / JBoss 7.2
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1297) deploy --url command creates invalid deployment
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1297?page=com.atlassian.jira.plugi... ]
Martin Simka commented on WFCORE-1297:
--------------------------------------
I think that deployment from url should be consistent with other deployment methods
deploy <some-path>/simple-servlet.war
creates deployment simple-servlet.war with root context /simple-servlet
so I think that taking only the last of the URL would be better
> deploy --url command creates invalid deployment
> -----------------------------------------------
>
> Key: WFCORE-1297
> URL: https://issues.jboss.org/browse/WFCORE-1297
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 2.0.6.Final
> Reporter: Martin Simka
> Assignee: Dominik Pospisil
>
> Command {{deploy --url=http://localhost/test/simple-servlet.war}}
> creates invalid deployment
> According to logs everything seems to be fine
> {noformat}
> 15:03:57,505 INFO [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /tmp/jboss-eap-7.0/standalone/data/content/5e/5e5709be9a06a9ed7bcb2100a4143400fea887/content
> 15:03:57,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "/test/simple-servlet.war" (runtime-name: "/test/simple-servlet.war")
> 15:03:58,238 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: //test/simple-servlet
> 15:03:58,320 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "/test/simple-servlet.war" (runtime-name : "/test/simple-servlet.war")
> {noformat}
> but web context {{http://localhost:8080//test/simple-servlet}} isn't accessible, it returns {{404 - Not Found}}.
> (simple-servlet.war doesn't contain jboss-web.xml, so no context root is defined there)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5480) SPEC JMS 2007 benchmark fails with AMQ214013: Failed to decode packet
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/WFLY-5480?page=com.atlassian.jira.plugin.... ]
Flavia Rainone commented on WFLY-5480:
--------------------------------------
Just to keep the Jira updated, I sent to Clebert privately everything he needs to reproduce this issue. Now that we know that the copied buffer at MessageImpl.getEncodedBuffer is the culprit for the wrong buffer size, we are in position to have this issue solved.
> SPEC JMS 2007 benchmark fails with AMQ214013: Failed to decode packet
> ---------------------------------------------------------------------
>
> Key: WFLY-5480
> URL: https://issues.jboss.org/browse/WFLY-5480
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Ondřej Kalman
> Assignee: Flavia Rainone
> Priority: Blocker
>
> But I have another problem, when I removed trace logs from config I'm not able to run benchmark on localhost to the end, because clients starts getting :
> AMQ214013: Failed to decode packet
> java.lang.IndexOutOfBoundsException: readerIndex: 2130706436 (expected: 0 <= readerIndex <= writerIndex(2943))
> at io.netty.buffer.AbstractByteBuf.readerIndex(AbstractByteBuf.java:73)
> at io.netty.buffer.WrappedByteBuf.readerIndex(WrappedByteBuf.java:99)
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readerIndex(ChannelBufferWrapper.java:405)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.decode(MessageImpl.java:1052)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.decodeFromBuffer(MessageImpl.java:459)
> at org.apache.activemq.artemis.core.protocol.core.impl.wireformat.SessionReceiveMessage.decode(SessionReceiveMessage.java:94)
> at org.apache.activemq.artemis.core.protocol.ClientPacketDecoder.decode(ClientPacketDecoder.java:42)
> at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:371)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$DelegatingBufferHandler.bufferReceived(ClientSessionFactoryImpl.java:1374)
> at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:242)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:847)
> at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteCha
> nnel.java:131)
> at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
> at java.lang.Thread.run(Thread.java:745)
> and
> Thread-9 (ActiveMQ-client-global-threads-1266561810): Uncaught exception.
> java.lang.NumberFormatException: null
> at java.lang.Integer.parseInt(Integer.java:542)
> at java.lang.Integer.valueOf(Integer.java:766)
> at org.apache.activemq.artemis.utils.TypedProperties.getIntProperty(TypedProperties.java:280)
> at org.apache.activemq.artemis.core.message.impl.MessageImpl.getIntProperty(MessageImpl.java:811)
> at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getIntProperty(ActiveMQMessage.java:578)
> at org.spec.jms.agents.SPECWorkerThread.receivedMessage(SPECWorkerThread.java:849)
> at org.spec.jms.agents.SPECWorkerThread.onMessage(SPECWorkerThread.java:820)
> at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:100)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1089)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1224)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Thread-3 (ActiveMQ-client-global-threads-1266561810): Uncaught exception.
> javax.jms.IllegalStateException: AMQ119027: Could not find reference on consumer ID=0, messageId = 104,833 queue = 127\.0\.0\.1_VM1_SPAgent7_0.SP_CallForOffersEH_7_EHID_1PF0
> at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:410)
> at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.sendACK(ActiveMQSessionContext.java:461)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.acknowledge(ClientSessionImpl.java:765)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.doAck(ClientConsumerImpl.java:1212)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.flushAcks(ClientConsumerImpl.java:830)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.flushAcks(ClientSessionImpl.java:1852)
> at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:501)
> at org.apache.activemq.artemis.core.client.impl.DelegatingSession.commit(DelegatingSession.java:159)
> at org.apache.activemq.artemis.jms.client.ActiveMQSession.commit(ActiveMQSession.java:218)
> at org.spec.jms.eventhandler.sp.SP_CallForOffersEH.handleMessage(SP_CallForOffersEH.java:306)
> at org.spec.jms.agents.SPECWorkerThread.onMessage(SPECWorkerThread.java:821)
> at org.apache.activemq.artemis.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:100)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1089)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1224)
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecut
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5898) JMS client BOM needs to include Apache Commons BeanUtils
by Juraci Paixão Kröhling (JIRA)
[ https://issues.jboss.org/browse/WFLY-5898?page=com.atlassian.jira.plugin.... ]
Juraci Paixão Kröhling commented on WFLY-5898:
----------------------------------------------
[~mnovak], I found this issue when working on this test:
https://github.com/jpkrohling/hawkular-metrics/blob/6e37afd7d87a74e090cb1...
>From what I remember, you can reproduce it by trying to run the test with and without the BeanUtils dependency, declared here:
https://github.com/jpkrohling/hawkular-metrics/blob/6e37afd7d87a74e090cb1...
Note that the "working" state, in the context of this JIRA, is still a test failure, as this branch never reached the master for that project. If I have some free cycles, I'll try to make a smaller reproducer for this.
> JMS client BOM needs to include Apache Commons BeanUtils
> --------------------------------------------------------
>
> Key: WFLY-5898
> URL: https://issues.jboss.org/browse/WFLY-5898
> Project: WildFly
> Issue Type: Bug
> Components: Application Client, JMS
> Affects Versions: 10.0.0.CR4
> Environment: Wildfly 10.0.0.CR4
> Reporter: Juraci Paixão Kröhling
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.CR5
>
>
> When using the JMS client BOM, the following exception happens, due to the missing transitive dependency on Apache Commons BeanUtils
> {code}
> Exception in thread "naming-client-message-receiver-1-thread-1" java.lang.NoClassDefFoundError: org/apache/commons/beanutils/BeanIntrospector
> at org.apache.activemq.artemis.uri.ConnectionFactoryParser.<init>(ConnectionFactoryParser.java:26)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:173)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:169)
> ...
> {code}
> As a workaround, the consumer of the BOM may to add the following dependency:
> {code}
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <version>1.9.2</version>
> <scope>test</scope>
> </dependency>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1302) Rename wildfly-launcher.jar to launcher.jar
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1302?page=com.atlassian.jira.plugi... ]
Tomaz Cerar moved JBEAP-2809 to WFCORE-1302:
--------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1302 (was: JBEAP-2809)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: (was: Productization)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 2.0.7.Final
(was: 7.0.0.ER2 (Beta))
> Rename wildfly-launcher.jar to launcher.jar
> -------------------------------------------
>
> Key: WFCORE-1302
> URL: https://issues.jboss.org/browse/WFCORE-1302
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 2.0.7.Final
> Reporter: Tomaz Cerar
> Assignee: Paul Gier
> Priority: Blocker
>
> File {{jboss-eap-7.0/bin/wildfly-launcher.jar}} should use prefix {{jboss}} instead of {{wildfly}} because of branding and to be consistent with {{jboss-cli-client.jar}} and {{jboss-client.jar}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5898) JMS client BOM needs to include Apache Commons BeanUtils
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-5898?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFLY-5898:
--------------------------------------
[~juraci.costa] Could you provide code which reproduce this issue? I did some tries but with no success. We need it for verification of this issue.
> JMS client BOM needs to include Apache Commons BeanUtils
> --------------------------------------------------------
>
> Key: WFLY-5898
> URL: https://issues.jboss.org/browse/WFLY-5898
> Project: WildFly
> Issue Type: Bug
> Components: Application Client, JMS
> Affects Versions: 10.0.0.CR4
> Environment: Wildfly 10.0.0.CR4
> Reporter: Juraci Paixão Kröhling
> Assignee: Jeff Mesnil
> Fix For: 10.0.0.CR5
>
>
> When using the JMS client BOM, the following exception happens, due to the missing transitive dependency on Apache Commons BeanUtils
> {code}
> Exception in thread "naming-client-message-receiver-1-thread-1" java.lang.NoClassDefFoundError: org/apache/commons/beanutils/BeanIntrospector
> at org.apache.activemq.artemis.uri.ConnectionFactoryParser.<init>(ConnectionFactoryParser.java:26)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:173)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:169)
> ...
> {code}
> As a workaround, the consumer of the BOM may to add the following dependency:
> {code}
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <version>1.9.2</version>
> <scope>test</scope>
> </dependency>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1012) kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1012?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1012:
-------------------------------------------------
Jiri Petrlik <jpetrlik(a)redhat.com> changed the Status of [bug 1293965|https://bugzilla.redhat.com/show_bug.cgi?id=1293965] from ON_QA to ASSIGNED
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1012
> URL: https://issues.jboss.org/browse/DROOLS-1012
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
> Attachments: brms-fuse-integration-master.tgz
>
>
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry. This implies that when the KieContainer is created in a OSGi environment it is not able to get an instance of the MavenClassLoaderResolver and then cannot create a ClassLoader including all the transitive dependencies of the kjar to be compiled.
> The attached project reproduces this issue. In order to run it, it's enough to do a mvn clean install of the project and issue the following commands in fuse:
> features:addurl mvn:com.redhat/brms-fuse-integration-features/0.0.1-SNAPSHOT/xml/features
> features:install brms-integration-bundle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months