[jira] [Commented] (BEAM-12012) ElasticsearchIO - Add API key & bearer token authentication

["Fabien Caylus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375703#comment-17375703 ] 

Fabien Caylus commented on BEAM-12012:
--------------------------------------

Hello ! Just checked on the issue after a while, and I realized that the issue in Jira was mark as "stale", however, the PR in Github was merged by [~heejong]. I'm not sure what are the next steps ?

> 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: 1h 20m
>  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)