Bug 1280313
Summary: | Multiple client command execution through SOAP interface does not authenticate correctly | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Tomas Livora <tlivora> |
Component: | Business Central | Assignee: | Shelly McGowan <smcgowan> |
Status: | CLOSED EOL | QA Contact: | Ivo Bek <ibek> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.2.0 | CC: | etirelli, ibek, lpetrovi, rrajasek |
Target Milestone: | CR2 | Keywords: | Regression |
Target Release: | 6.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-27 19:39:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomas Livora
2015-11-11 13:08:27 UTC
I have just tried it with BPMS 6.1 and exception is thrown there. However, the different one when the test is executed alone (RemoteCommunicationException) and with other SOAP tests (WebServiceException). In BPMS 6.2 there is the same exception when the test is executed alone (RemoteCommunicationException) and no exception if it is executed together with other SOAP tests. Tomas, Could you provide a test that reproduces this issue? I tried to reproduce the issue in several different ways but was unable to do so. At the moment, my suspicion is that this is not a bug, but a weird by-product of the QE tests. However, I've also been wrong about my suspicions quite often! Apologies Tomas, it took me a while, but all of a sudden I understood where the mistake was and what was happening. Please ignore the above comment. However, I do not believe this is a blocker. What I'm seeing is the following: 1. In certain situations, it's possible to _create a client_ with incorrect/unauthorized login information. 2. However, _requests_ with unauthorized login information are not succeeding. This means that the problem is only limited to the creation of clients and does not extend to unauthorized requests. Tomas and/or Lukash, could you confirm this? Marco, it seems that the SOAP client is working though it uses wrong credentials. I checked the jenkins jobs and the test passes all the assertions in the code below: RemoteController rc = new SOAPCommandController(TestConfig.getApplicationUrl(), IntegrationBase.DEPLOYMENT_ID, "IDontExist", "MyPassword"); ProcessInstance pi = rc.startProcess(DEPLOYMENT_ID, SCRIPT_TASK_PROCESS_ID, null); Assertions.assertThat(pi).isNotNull(); Assertions.assertThat(pi.getProcessId()).isEqualTo(SCRIPT_TASK_PROCESS_ID); Assertions.assertThat((long) pi.getState()).isEqualTo(ProcessInstance.STATE_COMPLETED); And the test fails with java.lang.AssertionError: Expected exception: org.kie.remote.client.api.exception.RemoteCommunicationException In the log I can see the process instance too. ProcessInstance 1133 [processId=org.jboss.qa.bpms.ScriptTask,state=2] Maciej has found a likely fix: https://github.com/droolsjbpm/droolsjbpm-integration/pull/236/files?w=1 I've confirmed that the same class (AuthValueImpl) also exists in the IBM and Open JDK. PR's submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/238 https://github.com/droolsjbpm/droolsjbpm-integration/pull/237 The following code, if executed before the test, provides a workaround: https://github.com/mrietveld/droolsjbpm-integration/blob/pr-BZ-1280313/kie-remote/kie-remote-client/src/main/java/org/kie/remote/client/ws/KieRemoteWsAuthenticator.java#L81-L107 QE, would it be possible for you to verify this workaround on the test today? (Nov 24th) (In reply to Marco Rietveld from comment #15) > QE, would it be possible for you to verify this workaround on the test > today? (Nov 24th) Unfortunately not. :-( Everybody gone already. First thing in the morning, though. Marco, I have just tested it and our reproducer passes when I execute that method before each test. So it seems the issue is fixed by this workaround. Fixed. Commits: 6.3.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/594fa3e1 master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/662231c0 Verified in BPM Suite 6.2.0.CR2 |