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.
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?
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/453
This bug has been rejected for 6.3.0, and a new bug has been made for 6.3.1, so I am closing this bug. The issue has been fixed, however. Commits: 6.4.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/9a6ce0fd master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/0a38844e