L3 - Default At the moment authentication to Elasticsearch can be configured using Basic Authentication. In some scenarios, customers are configuring other means for Elasticsearch authentication (e.g. Token-Based Authentication).
What is the desired functionality that you are missing?
The ability to add custom authorization headers to requests made against the configured Elasticsearch instance in Optimize. The tokens added in headers can expire, so Optimize needs to add headers on a per-request basis
Acceptance Criteria:
Given I have a plugin configured that adds a custom authorization header
When Optimize makes any request against Elasticsearch during operation **
Then the custom header is included in each request
Given I have a plugin configured that adds a custom authorization header
When Optimize makes any request against Elasticsearch during Upgrade
Then the custom header is included in each request during the upgrade
Hint:
Headers can be added as part of the request options: https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-low-usage-requests.html
This is the controller panel for Smart Panels app
1.
|
Allow insertion of authorization headers through a configured plugin |
|
Done | Unassigned |
2.
|
Allow configured plugins to add authentication headers for upgrade requests |
|
Done | Unassigned |
3.
|
Allow addition of custom headers for Reimporter |
|
Done | Unassigned |
4.
|
Test the custom header plugin |
|
Done | Unassigned |
5.
|
Add documentation for plugin usage |
|
Done | Unassigned |
6.
|
Add example plugin to our example repo |
|
Done | Unassigned |