[
https://issues.apache.org/jira/browse/BOOKKEEPER-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591660#comment-15591660
]
Enrico Olivelli commented on BOOKKEEPER-959:
--------------------------------------------
My idea is to introduce some standard message types to be used on the wire.
Actually in order to implement an "usual" authentication protocol it is enough
to exchange simple byte[] values.
Usually I use SASL (for MD5 o GSSAPI/Kerberos....) and in order to use Java
built-in SASL feature a byte[] is enough, then SASL encapsulated all the state.
A byte[] can be used to transport any kind of custom information, such as
JSON/XML formatted data, I think it will be fine
I will work on a first patch and share some code
> ClientAuthProvider and BookieAuthProvider Public API used Protobuf Shaded
> classes
> ---------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-959
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-959
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.4.0
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
> Priority: Blocker
> Fix For: 4.5.0
>
>
> With 4.4.0 we introduced the ability to implement custom authentication
> plugins.
> The new interfaces ClientAuthProvider and BookieAuthProvider depend on
> ExtensionRegistry, which is a shaded dependency.
> As a consequence it is not possibile to implement any custom auth provider in
> code outside the project, because shaded/relocated dependencies cannot be
> used.
> We need to break the actual interface and introduce a new way to implement
> such plugins in a portable way
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
