[
https://issues.apache.org/jira/browse/BEAM-12012?focusedWorklogId=576147&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-576147
]
ASF GitHub Bot logged work on BEAM-12012:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Apr/21 15:38
Start Date: 02/Apr/21 15:38
Worklog Time Spent: 10m
Work Description: fcaylus commented on pull request #14345:
URL: https://github.com/apache/beam/pull/14345#issuecomment-812582790
Hi @ihji . Thanks for your feedback ! I fixed the arguments check in a first
commit. I'll try to find a way to test the headers, and push a fix for that
too. I'll keep you updated on that.
Note: Yes @pabloem, it was. Thanks too for dispatching the PR to the correct
person.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 576147)
Time Spent: 50m (was: 40m)
> ElasticsearchIO - Add API key & bearer token authentication
> -----------------------------------------------------------
>
> Key: BEAM-12012
> URL: https://issues.apache.org/jira/browse/BEAM-12012
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Fabien Caylus
> Assignee: Fabien Caylus
> Priority: P3
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hello !
> Currently, only username/password authentication is supported in this IO.
> However, Elasticsearch also supports:
> * [API
> key|https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-api-key.html],
> since version 6.7
> * [Bearer
> token|https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-token.html],
> since version 6.3
> Supporting them would allow the user to create specific keys or tokens (with
> specific permissions and validity period) and use them for its jobs.
> However, both features are not opensource themselves inside Elasticsearch
> (part of the X-Pack solution, under the Elastic license). But for the
> implementation in Beam, it's only a matter of setting the correct
> {{Authorization}} header. So I think it should be ok to implement them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
