Bug 1327632

Summary: [GPS](6.2.z)Support for custom authentication in RemoteRuntimeEngine configuration
Product: [Retired] JBoss BPMS Platform 6 Reporter: Alessandro Lazarotti <alazarot>
Component: Business CentralAssignee: Shelly McGowan <smcgowan>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: high    
Version: 6.2.0CC: etirelli, ksuta, kverlaen, rrajasek, rsynek, selrahal, smcgowan
Target Milestone: CR1   
Target Release: 6.2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1325986 Environment:
Last Closed: 2020-03-27 19:40:19 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1325986, 1329766    
Bug Blocks: 1327763, 1327765    

Description Alessandro Lazarotti 2016-04-15 14:09:59 UTC
+++ This bug was initially created as a clone of Bug #1325986 +++

Currently the RemoteRuntimeEngine API only allows a username and password to be specified and works solely with HTTP Basic authentication. For custom authentication we will have access to a session cookie and need to pass that along in every HTTP request to Business Central. The minimal functionality required would be the ability to set a header/cookie value on each http request, although perhaps just an extensible way of modifying the http requests would enable future authentication/authorization extensions.

--- Additional comment from JBoss Product and Program Management on 2016-04-11 10:20:08 EDT ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 2 Marco Rietveld 2016-04-22 22:26:38 UTC
The following has been agreed with with GSS: 

This bug is for the following feature: 

- Allow 1 or more custom headers to be set per kie-remote-client instance to the REST execute method that the kie-remote-client uses. 
- This header will be sent with each HTTP request that the kie-remote-client instance sends. 

No other functionality can be associated with this bugzilla. 
Other functionality besides the functionality described above should be addressed in different bugzillas.

Comment 3 Marco Rietveld 2016-04-22 22:42:39 UTC
Pull request submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/452

Comment 5 Edson Tirelli 2016-04-26 13:58:53 UTC
Setting as MODIFIED as the changes discussed so far were included in the patch. If additional changes are required, please open a new ticket to track it.

Comment 6 Karel Suta 2016-05-06 14:57:18 UTC
Verified in 6.2.3 CR1.
Headers defined in remote client are sent to Business central.

Comment 7 Marco Rietveld 2016-05-11 12:25:07 UTC
Commit: 

6.3.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/2ccb9d5c