+++ 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.
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.
Pull request submitted: https://github.com/droolsjbpm/droolsjbpm-integration/pull/452
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.
Verified in 6.2.3 CR1. Headers defined in remote client are sent to Business central.
Commit: 6.3.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/2ccb9d5c