Robert DiPietro <[email protected]> writes: > Hello! > > I have been deving against a Derby DB on which requireAuthentication > is true, the provider is built-in, and all users have been defined in > the derby.properties file (so they are all system level users). This > has been extremely convenient in development, however there are > obvious concerns about having the password stored in plaintext in a > file. > > Is it possible to require authentication in built-in mode, but have no > system level users defined in derby.properties, rather only defined at > database level (stored internally on the database)? > > For example, I have tried disabling requireAuthentication, logging in > to the system, creating a db, and then creating a user against it > using these commands: > > CALL > SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('Derby.database.propertiesOnly','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.username', > 'password'); > > Which seems to work, but then if I enable requireAuthentication in > derby.properties, I can no longer log in.
Hi Robert, The property names should start with 'derby' (all lowercase), not 'Derby'. Does it work as expected if you change the case of the initial letter? -- Knut Anders
