Details
-
Enhancement
-
Resolution: Done
-
Major
-
6.3.0.GA
-
None
-
Release Notes
-
ER2
Description
Currently the Decision Server client 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 Decision Server. 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.
It is known that the KieServicesConfiguration object supports a ConnectionProvider object:
configuration.setCredentialsProvider(new org.kie.server.client.CredentialsProvider() { @Override public String getHeaderName() { // TODO Auto-generated method stub return null; } @Override public String getAuthorization() { // TODO Auto-generated method stub return null; } });
However, the requirement is to set multiple custom HTTP header and have the possibility to change for every request made by the client.
Attachments
Issue Links
- is cloned by
-
RHBRMS-2535 [GSS](6.3.z) Support for custom HTTP headers in Decision Server java client configuration
- Verified