List of all connection (JDBC) attributes by the system.
This class exists for two reasons
To act as the internal documentation for the attributes.
To remove the need to declare a java static field for the attributes
name in the protocol/implementation class. This reduces the footprint as
the string is final and thus can be included simply as a String constant pool entry.
This class should not be shipped with the product.
This class has no methods, all it contains are String's which by
are public, static and final since they are declared in an interface.
At some point this class should be replaced by
org.apache.derby.shared.common.reference.Attribute.
The issue is that this class is used by ij to check attributes,
ij uses reflection on this class to get the list of valid attributes.
The expanded class in shared has the client attributes as well.
Ideally ij would work of an explicit list of attributes and not
infer the set from reflection. See DERBY-1151
If dataEncryption is true, use this attribute to pass in the
secret key. The secret key must be at least 8 characters long.
This key must not be stored persistently in cleartext anywhere.
This attribute is used to request to create a database from backup.
This will throw error if a database with same already exists at the
location where we tring to create.
Attribute for encrypting a database.
Specifies the actual key. When this is specified
all the supplied crypto information is stored
external to the database, ie by the application.
One can encrypt the database with an encryption key at create time.
For security reasons, this key is not made persistent in the database.
But it is necessary to verify the encryption key whenever booting the database
before we access the data/logs to avoid the risk of corrupting the database because
of a wrong encryption key.
This attribute refers to the name of the file where encrypted data is stored for
verification of encryption key.
Internal attributes. Mainly used by DRDA and Derby BUILTIN
authentication provider in some security mechanism context
(SECMEC_USRSSBPWD).
DRDA_SECTKN_IN is the random client seed (RDs)
DRDA_SECTKN_OUT is the random server seed (RDr)
The attribute that is used to chage the secret key of an encrypted
database. The secret key must be at least 8 characters long.
This key must not be stored persistently in cleartext anywhere.
The attribute that is used to chage the encryption
key of an encrypted database. When this is specified
all the supplied crypto information is stored
external to the database, ie by the application.
This attribute is used to request a database restore from backup.
It must be used only when the active database is corrupted,
because it will cleanup the existing database and replace
it from the backup.