Hi Stefan,
I am not able to reproduce the behavior you are seeing. The following
script works fine for me when I use Derby 10.8.2.2:
connect 'jdbc:derby:memory:db;create=true';
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication',
'true');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.authentication.provider',
'BUILTIN');
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.DBUSER1',
'password');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.defaultConnectionMode',
'readOnlyAccess');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.fullAccessUsers',
'DBUSER1');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.propertiesOnly','false');
connect 'jdbc:derby:memory:db;shutdown=true';
-- fails because authentication is on but no password is supplied
connect 'jdbc:derby:memory:db;user=DBUSER1';
-- succeeds
connect 'jdbc:derby:memory:db;user=DBUSER1;password=password';
-- succeeds
call SYSCS_UTIL.SYSCS_BACKUP_DATABASE( 'backups' ) ;
A further comment inline...
On 11/26/12 11:31 AM, Stefan R. wrote:
Hi,
in one of our web apps we activated derbys builtin user authentication
for the databases. We are using Derby 10.8.2.2
The app is triggering a backup task, which executes
SYSCS_UTIL.SYSCS_BACKUP_DATABASE over a JDBC connection. This throws
an exception saying: the connection could not be authorized.
This suggests that the app couldn't even establish a connection. The app
never got to the step of attempting a backup. I would recommend
double-checking the credentials.
Hope this helps,
-Rick
The following statements have been used to activate authentication:
--------------------
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.connection.requireAuthentication',
'true');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.authentication.provider', 'BUILTIN');
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.DBUSER1',
'password);
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.defaultConnectionMode',
'readOnlyAccess');
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.fullAccessUsers',
'DBUSER1);
CALL
SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.database.propertiesOnly','false');
--------------------
So, DBUSER1 should have full access.
Are there any restrictions to SYSCS_UTIL functions for
fullAccessUsers? How to authorize these?
Thanks for your input,
Stefan
