kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zander (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4570) How to transfer extended fields in producing or consuming requests.
Date Tue, 10 Jan 2017 07:41:58 GMT

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

zander commented on KAFKA-4570:
-------------------------------

[~ewencp] In my use case, the user  has  Access Key and Secret Key and he will sign the content.
For each produce or fetch request, the server need to verify the sign using the user's Public
Key.
I checked the authentication tools currently supported. It seems that my demand cannot be
satisfied now.


> How to transfer extended fields in producing or consuming requests.
> -------------------------------------------------------------------
>
>                 Key: KAFKA-4570
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4570
>             Project: Kafka
>          Issue Type: Wish
>          Components: clients
>    Affects Versions: 0.10.1.1
>            Reporter: zander
>            Priority: Critical
>              Labels: features
>
> We encounter a problem that  we can not transfer extended fields for producing or consuming
requests to the broker.
> We want to validate  the producers or consumers in a custom way other than using SSL.
> In general, such as JMS, it is possible to transfer user-related fields to server.
> But it seems that Kafka dose not support this, its protocol is very tight and  unable
to add user-defined fields.
> So is there any way  achieving this goal ?



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

Mime
View raw message