You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Fabien Caylus (Jira)" <ji...@apache.org> on 2021/03/26 13:21:00 UTC
[jira] [Assigned] (BEAM-12012) ElasticsearchIO - Add API key &
bearer token authentication
[ https://issues.apache.org/jira/browse/BEAM-12012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabien Caylus reassigned BEAM-12012:
------------------------------------
Assignee: Fabien Caylus
> 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
>
> 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.
>
> I'm thinking on working on this if it's ok.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)