Re-reading your message I now understand what you are saying. You wish to
update the OPTIONS response sent pre SASL.
I’m still not sure that’s actually required. The SASL
Authenticate/Auth_Response can be what ever you want it to be. As long as what
you implement supports recognizing/falling bac
I think you are talking about the SASL handshake? The authenticator can
override the SASL handler for the connections. The negotiating authenticator
just needs to implement that override? You can then implement the flow you
mentioned.
At DataStax we do basically exactly that to support negoti
A negotiating authenticator is appealing, but I'm concerned that it
doesn't have a good migration story. If a client has not been configured
with a "negotiating provider" before it attempts to connect to a node
with a negotiating authenticator, the results will be unpredictable.
Today, the AUTH
Is there a dependency on Java 23 to make the `ant javadoc` tooling
to work? My understanding is that this change is coming in the
newer Java versions.
On 2024/12/02 15:30:14 Branimir Lambov wrote:
> Hello,
>
> What is the community's stand on using the new Markdown variation of
> JavaDoc?
> https
+1 for more code (github/ide) readable in-code documentation.
Do we use javadoc anywhere anymore, or read its generated apidocs
anywhere ? We removed that target from the build cycle, and don't
publish those artefacts or deploy the apidocs anywhere anymore… I
would say folk are either got the c
