Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Flume >> mail # user >> Authentication - Avro Source, Sink, RpcClient


+
Rakos, Rudolf 2013-01-23, 11:45
Copy link to this message
-
Re: Authentication - Avro Source, Sink, RpcClient
I agree that AvroSource/Sink SASL and Kerberos auth would be really useful.
It would need some work at the Avro level, though.

There is also the possibility of doing the same thing on top of Thrift, in
which case it would require a brand new source/sink/client implementation
but it wouldn't require any protocol work AFAICT.

Regards
Mike
On Wed, Jan 23, 2013 at 3:45 AM, Rakos, Rudolf <
[EMAIL PROTECTED]> wrote:

>   Hi Flume Users,****
>
> ** **
>
> We’d like to have authentication between Flume Nodes and Clients.****
>
> I believe that currently there’s no easy way to set up any kind of
> authentication between Avro Sources, Sinks, and RpcClients.****
>
> ** **
>
> I would like to ask what would be the best way to extend Flume to support
> authentication?****
>
> Would it be enough to extend or rewrite Avro Source, Sink and RpcClient?**
> **
>
> Does Avro or Netty support authentication?****
>
> ** **
>
> We’d prefer using Kerberos or maybe SPNEGO, but I’m not sure what options
> do we have.****
>
> ** **
>
> Thanks and regards,****
>
> Rudolf****
>
> ** **
>
> Rudolf Rakos
> *Morgan Stanley | ISG Technology
> *Lechner Odon fasor 8 | Floor 06
> Budapest, 1095
> Phone: +36 1 881-4011
> [EMAIL PROTECTED]
>
>
> Be carbon conscious. Please consider our environment before printing this
> email.
>    ****
>
>
> ------------------------------
>
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the
> opinions or views contained herein are not intended to be, and do not
> constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall
> Street Reform and Consumer Protection Act. If you have received this
> communication in error, please destroy all electronic and paper copies and
> notify the sender immediately. Mistransmission is not intended to waive
> confidentiality or privilege. Morgan Stanley reserves the right, to the
> extent permitted under applicable law, to monitor electronic
> communications. This message is subject to terms available at the following
> link: http://www.morganstanley.com/disclaimers If you cannot access these
> links, please notify us by reply message and we will send the contents to
> you. By messaging with Morgan Stanley you consent to the foregoing.
>
>
+
Rakos, Rudolf 2013-01-25, 14:07
+
Mike Percy 2013-02-05, 08:33
+
Rakos, Rudolf 2013-02-05, 10:50
+
Mike Percy 2013-02-05, 14:45
+
Rakos, Rudolf 2013-02-07, 09:29