Bug 1329766 - [GPS](6.3.z)Support for custom authentication in RemoteRuntimeEngine configuration
Summary: [GPS](6.3.z)Support for custom authentication in RemoteRuntimeEngine configur...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Shelly McGowan
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On: 1325986
Blocks: 1327632
TreeView+ depends on / blocked
 
Reported: 2016-04-22 22:47 UTC by Alessandro Lazarotti
Modified: 2020-03-27 19:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1325986
Environment:
Last Closed: 2020-03-27 19:43:38 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)

Description Alessandro Lazarotti 2016-04-22 22:47:08 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.

--- Additional comment from Alessandro Lazarotti on 2016-04-15 10:12:31 EDT ---

removing the bpms-rollup-3-6.2.x flag, i just cloned it to Bug 1327632

--- Additional comment from Tomas Livora on 2016-04-20 10:01:08 EDT ---

Hi Sal,
what kind of custom authentication are you talking about? Can you elaborate a little bit more on how exactly the customer wants to use this?

--- Additional comment from Marco Rietveld on 2016-04-22 18:27:00 EDT ---

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.

--- Additional comment from Marco Rietveld on 2016-04-22 18:42:28 EDT ---

Pull request submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/453

Comment 2 Marco Rietveld 2016-05-11 12:19:38 UTC
Fixed. Commits: 

6.4.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/9a6ce0fd

Comment 3 Marco Rietveld 2016-05-11 12:23:11 UTC
Also fixed on the 6.3.x and master branches: 

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

master:
https://github.com/droolsjbpm/droolsjbpm-integration/commit/0a38844e


Note You need to log in before you can comment on or make changes to this bug.