Something we will have to be a little careful with here is the licensing. Sadly shield is only available under a commercial license, so we will not be able to include the shield client components in an Apache project. This will make it difficult to take this PR. We can certainly look at ways of incorporating the config elements, but the actual dependencies may have to be a case of documented install over the project rather than actual dependencies. Not sure what the implications will be for the client build, but we may be able to abstract that out sufficiently to make it compatible.
Simon > On 30 Nov 2016, at 13:58, [email protected] <[email protected]> wrote: > > Jesse, do you have a ticket open for this work? I wasn't able to find one, > but if you do please share it here, otherwise would you mind putting one > in? That's the best method we currently have to track who is working on > what. Thanks, > > Jon > > On Wed, Nov 30, 2016 at 8:55 AM Jesse Throwe <[email protected]> > wrote: > >> Morning Prashant, >> >> I’m actively working on a PR for this. You can check my working branch at >> https://github.com/atopian/incubator-metron/tree/elastic_shield >> >> - Jesse >> >> On 11/30/16, 8:40 AM, "Prashant Bhalesain" <[email protected]> wrote: >> >>> Hi >>> >>> Is anyone aware if metron can work with Shiled/x-pack authentication? I >>> need to make metron work with ssl enabled elastic cluster and >>> authentication. >>> If not, if there is any plan for it or any other alternate way to achieve >>> secured functionality with elastic search? >>> >>> I didnt see anything related to authorization in the code yet, may be I am >>> looking at wrong place. >>> >> https://github.com/apache/incubator-metron/blob/master/metron-platform/metron-elasticsearch/src/main/java/org/apache/metron/elasticsearch/writer/ElasticsearchWriter.java >>> >>> Best >>> Prashant >> >> This electronic transmission is confidential and intended solely for the >> addressee(s). If you are not an intended addressee, do not disclose, copy >> or take any other action in reliance on this transmission. If you have >> received this transmission in error, please delete it from your system and >> notify CoverMyMeds LLC at [email protected]. Thank you. >> > -- > > Jon > > Sent from my mobile device
