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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-12012:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>              Labels: stale-assigned
>          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)