Legal values include:
NATIVE authentication using credentialsDB, a dedicated database, to store user credentials. This value must be set by using system-wide Java Virtual Machine (JVM) properties or by using the derby.properties file; it cannot be set in the database by using the SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY system procedure. When this system-wide value is set, credentialsDB is used to authenticate all operations. Individual databases can override this directive by specifying their own value for derby.authentication.provider.
The value of credentialsDB must be a valid name for a database.
NATIVE authentication using credentialsDB for system-wide operations,
but using an individual database's
An external LDAP directory service.
A user-defined class that provides user authentication.
For more information about these settings, see "Configuring NATIVE
authentication" and "Configuring LDAP authentication" in the
To enable any
When using NATIVE authentication, you can also set the following related properties:
When using NATIVE authentication, the database owner calls the
When using NATIVE authentication, any user can call the
For more information about user authentication, see "Configuring user
authentication" in the
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
No authentication.
Static. For system-wide properties, you must reboot