[
https://issues.apache.org/jira/browse/KNOX-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487906#comment-16487906
]
Dequan Chen commented on KNOX-1155:
-----------------------------------
To [~lmccay],
A separate Jira, as per your suggest, was created
(https://issues.apache.org/jira/browse/KNOX-1332). The actual documentation was
created based on what you said - you will add back the explicit policy rule
<policy role="authentication" name="Anonymous"/> to the service.xml file. It
has been attached to the new Jira as a Word file.
Dequan
> Knox Gateway Service for ElasticSearch
> --------------------------------------
>
> Key: KNOX-1155
> URL: https://issues.apache.org/jira/browse/KNOX-1155
> Project: Apache Knox
> Issue Type: New Feature
> Components: Build, Release
> Affects Versions: 0.9.0, 0.9.1, 0.10.0, 0.11.0
> Environment: Knox Gateway Servers
> Reporter: Dequan Chen
> Assignee: Dequan Chen
> Priority: Critical
> Labels: patch
> Fix For: 1.1.0
>
> Attachments: KNOX-1155-001.patch, KNOX-1155-002.patch, rewrite.xml,
> service.xml
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> We have used a lot of Knox Gateway Services and ElasticSearch service on our
> Big Data platforms. However there are no Knox Gateway Service for
> ElasticSearch yet. In our situation, we need such a Knox Gateway Service for
> ElasticSearch without Knox to do the …
> authentication but ElasticSearch Rest Server(s) to do the authentication. As
> per our use case, we have developed such a Knox Gateway ElasticSearch Service
> (services/elasticsearch/1.0.0), and we are in a mode to share the code to the
> Apache Knox community because it has been fully tested for the following
> scenarios:
> (1) No-LDAP, Local-LDAP or company-specific-LDAP authentication in the Knox
> gateway;
> (2) Any Elasitcsearch Index - creation, deletion, refresshing and data -
> writing, updating and retrieval;
> (3) Elasticsearch node root query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
