[jira] [Commented] (METRON-503) Metron REST API

["Larry McCay (JIRA)" <ji...@apache.org>]

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

Larry McCay commented on METRON-503:
------------------------------------

Hi [~rmerriman] - this looks interesting.

There is a good bit of overlap with what Apache Knox could provide though.

Since Knox already provides the pluggable authentication and authorization integrations - including Apache Ranger and the fact that it already proxies a number of Hadoop services, maybe you should consider adding JAXRS services for Metron to Knox.

Knox already has support for the following authentication mechanism and has a pluggable framework for adding more:
* HTTP Basic Auth against AD/LDAP (most commonly used)
* SPNEGO/Kerberos
* HTTP Header-based Preauthentication for solutions like Siteminder, Tivoli Access Manager
* It also has WebSSO capabilities for CAS, SAML (Okta), a Knox Form-based provider, OAuth for Google, Facebook, etc.

WebSec things like CORS and CSRF are also already covered for APIs hosted and proxied by Knox gateway.

Knox also already provides access to:
* Ambari
* WebHDFS (HDFS)
* Templeton (HCatalog)
* Stargate (HBase)
* Oozie
* Hive/JDBC
* Yarn RM
* Storm

Another thing to consider when proxying the Hadoop services is that many of the services have a proprietary HA protocol built into the API. You have to know what various failure conditions mean and what messages to expect and interpret. Knox already takes care of that as well.

There are a couple examples in the Knox codebase for hosting JAXRS REST service directly in Knox as well.
Look at the KnoxSSO service and the Admin API for Knox as examples.

Swagger support would be great to add and has been on the roadmap for Knox for a while.
Would love to be able to convert the WADL served by the backend services into swagger but there really isn't enough detail to do so properly - AFAICT.

Anyway, just a thought.

> Metron REST API
> ---------------
>
>                 Key: METRON-503
>                 URL: https://issues.apache.org/jira/browse/METRON-503
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Ryan Merriman
>            Assignee: Ryan Merriman
>         Attachments: Metron REST API.docx
>
>
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this Jira includes adding a REST API to Metron.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)