At the moment, there is no special support for HTTP authentication in WebView, so if an application requires HTTP authentication, it is expected to make use of whatever the java.net.* stack has to offer in that area.

Normally, if the application wants to use specific credentials when connecting to a specific host, it can create a sub-class of java.net.Authenticator, implement the getPasswordAuthentication method in it, and install an instance of the subclass as the default authenticator by calling Authenticator.setDefault. This ability to customize HTTP authentication is already present in Java and is fully compatible with WebView.

The only problem with Authenticator.setDefault is that it affects the entire JVM. WebView could try to address this problem by adding the ability to specify an Authenticator or equivalent callback object per WebEngine rather than for the entire JVM.