[
https://issues.apache.org/jira/browse/KAFKA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706097#comment-14706097
]
ASF GitHub Bot commented on KAFKA-1683:
---------------------------------------
GitHub user gwenshap opened a pull request:
https://github.com/apache/kafka/pull/155
KAFKA-1683: persisting session information in Requests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gwenshap/kafka KAFKA-1683
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/155.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #155
----
commit d97449d3626c1a209eefa2eb01e011ecdec4f147
Author: Gwen Shapira <csh...@gmail.com>
Date: 2015-08-21T01:46:49Z
persisting session information in Requests
----
> Implement a "session" concept in the socket server
> --------------------------------------------------
>
> Key: KAFKA-1683
> URL: https://issues.apache.org/jira/browse/KAFKA-1683
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Affects Versions: 0.9.0
> Reporter: Jay Kreps
> Assignee: Gwen Shapira
> Fix For: 0.8.3
>
> Attachments: KAFKA-1683.patch, KAFKA-1683.patch
>
>
> To implement authentication we need a way to keep track of some things
> between requests. The initial use for this would be remembering the
> authenticated user/principle info, but likely more uses would come up (for
> example we will also need to remember whether and which encryption or
> integrity measures are in place on the socket so we can wrap and unwrap
> writes and reads).
> I was thinking we could just add a Session object that might have a user
> field. The session object would need to get added to RequestChannel.Request
> so it is passed down to the API layer with each request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
