Function
Specifies the authentication provider
for Derby user
authentication.
Legal values include:
- LDAP
An external LDAP directory service.
- A complete Java class name
A user-defined class that provides user
authentication.
- BUILTIN
Derby's
simple internal user authentication repository.
Important: Derby's
BUILTIN authentication mechanism is suitable only for development and testing
purposes. It is strongly recommended that production systems rely on LDAP or a
user-defined class for authentication. It is also strongly recommended that
production systems protect network connections with SSL/TLS.
When using an external authentication service provider (LDAP), you must also
set:
When using LDAP, you can set other LDAP-specific properties. See also:
Alternatively, you can write your own class to provide a different external
authentication service. This class must implement the public interface
org.apache.derby.authentication.UserAuthenticator and throw exceptions
of the type java.sql.SQLException where appropriate. Using a user-defined
class makes Derby adaptable
to various naming and directory services. For example, the class could allow
Derby to hook up to an
existing user authentication service that uses any of the standard directory and
naming service providers to JNDI.
To enable any Derby user
authentication, you must set the
derby.connection.requireAuthentication
property to true.
For more information about user authentication, see the Derby Developer's Guide.
Dynamic or static
Static. For system-wide properties, you must reboot
Derby for the change to take
effect. For database-wide properties, you must reboot the database for the
change to take effect.