The behavior of the undocumented Java Web Start property javaws.cfg.jauthenticator, with a value of none needs to be fully supported
and documented in future releases. Without this undocumented property, users of the SocksV5 protocol and JaWS are forced to authenticate using the default JRE authenticator dialog boxes. This type of authentication does not fit with the authentication scheme for most integrated applications.

When the JRE Authenticator is turned off with the -Djavaws.cfg.jauthenticator=none property set, the SocksV5 authentication
then goes to the preferences of java.net.socks.username and java.net.socks.password, and if that is not found, then the property user.name is used. That hierarchy of authentication also needs to be supported going forward in future releases when using SocksV5.