GSSCredential

[David Lloyd]

Essentially, the callback handler is a consumer of an array of
callback objects, which perform different functions by type such as
collecting a user name or password.  If a given callback type is not
supported by the callback handler, a specific exception is thrown
which indicates to the mechanism to indicate that fact.  The
authenticator might fall back to other strategies or mechanisms in
this case.

On Wed, Jun 12, 2019 at 11:31 AM Mark Rotteveel <mark at lawinegevaar.nl> wrote:
>
> On 2019-06-12 15:37, David Lloyd wrote:
> > On Wed, Jun 12, 2019 at 8:01 AM Mark Rotteveel <mark at lawinegevaar.nl>
> > wrote:
> >> Declaring it as `requires static` brings us full circle again. It will
> >> work for simple usages, but it will break for any implementation out
> >> there that proxies instances of ConnectionBuilder.
> >>
> >> We might be able to accept this risk. I have never seen use of
> >> ConnectionBuilder in the wild, and I actually haven't implemented it
> >> myself in Jaybird yet (nor have I seen it implemented in other open
> >> source drivers yet). We should be prepared to change this to
> >> `requires`
> >> instead if it proves to be problematic though.
> >
> > What about using the general-purpose authentication callback mechanism
> > used by JAAS and SASL instead of providing credentials?  That could
> > decouple JDBC from any particular authentication strategy altogether.
>
> I don't have experience with either of those, so, what would the API for
> that look like, and how would it work implementationwise?
>
> Mark



-- 
- DML