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

Tim Crowder commented on ZOOKEEPER-1525:
----------------------------------------

Hi Michi-

That got me further along, but now I'm getting:
  The specified diff file could not be parsed.
  Line 2: No valid separator after the filename was found in the diff header
>From the same patch-file as attached to this bug.
Note: I tried editing the patch, but didn't find a way to make ReviewBoard 
happy.
Jenkins clearly understood the patch as it built and tested it.

Is there a special format or anything else I need for ReviewBoard?
Is there a way to have ReviewBoard pick it up from this bug?

Thanks!
.timrc


> Plumb ZooKeeperServer object into auth plugins
> ----------------------------------------------
>
>                 Key: ZOOKEEPER-1525
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.5.0
>            Reporter: Warren Turkal
>            Assignee: Warren Turkal
>             Fix For: 3.5.1
>
>         Attachments: ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch, 
> ZOOKEEPER-1525.patch
>
>
> I want to plumb the ZooKeeperServer object into the auth plugins so that I 
> can store authentication data in zookeeper itself. With access to the 
> ZooKeeperServer object, I also have access to the ZKDatabase and can look up 
> entries in the local copy of the zookeeper data.
> In order to implement this, I make sure that a ZooKeeperServer instance is 
> passed in to the ProviderRegistry.initialize() method. Then initialize() will 
> try to find a constructor for the AuthenticationProvider that takes a 
> ZooKeeperServer instance. If the constructor is found, it will be used. 
> Otherwise, initialize() will look for a constructor that takes no arguments 
> and use that instead.



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

Reply via email to