[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561074#action_12561074
]
Rick Hillegas commented on DERBY-2109:
--------------------------------------
Just to clarify that username/password credentials are case-sensitive, I ran
the following experiment: I created my own UserAuthenticator implementation,
wired it into derby.properties, and then connected. The custom
UserAuthenticator printed out the arguments which Derby passed to it. Those
arguments are case sensitive, so it is up to the UserAuthenticator to determine
the rules it wants to enforce.
Here is my custom UserAuthenticator:
import org.apache.derby.authentication.UserAuthenticator;
import java.util.Properties;
import java.sql.SQLException;
/**
* Dummy authenticator. All users are legal
*
* @see org.apache.derby.authentication.UserAuthenticator
*/
public class DummyAuthenticator implements UserAuthenticator
{
public DummyAuthenticator() {}
/**
* Authenticate the passed-in user's credentials.
* A more complex class could make calls
* to any external users directory.
*
* @param userName The user's name
* @param userPassword The user's password
* @param databaseName The database
* @param infoAdditional jdbc connection info.
* @exception SQLException on failure
*/
public boolean authenticateUser(String userName,
String userPassword,
String databaseName,
Properties info)
throws SQLException
{
System.out.println( "userName = " + userName + "\nuserPassword = " +
userPassword + "\ndatabaseName = " + databaseName );
System.out.println( "info = " + info );
return true;
}
}
Here is my derby.properties:
derby.connection.requireAuthentication=true
derby.authentication.provider=DummyAuthenticator
And here is an ij script showing how this behaves at run-time:
ij version 10.4
ij> connect 'jdbc:derby:derby10.4;user=myHumbleSelf;password=myHumblePassword';
userName = myHumbleSelf
userPassword = myHumblePassword
databaseName = derby10.4
info = {user=myHumbleSelf, password=myHumblePassword}
ij> select count(*) from sys.systables;
1
-----------
24
1 row selected
ij> userName = null
userPassword = null
databaseName = null
info = {shutdown=true}
> System privileges
> -----------------
>
> Key: DERBY-2109
> URL: https://issues.apache.org/jira/browse/DERBY-2109
> Project: Derby
> Issue Type: New Feature
> Components: Security
> Affects Versions: 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Martin Zaun
> Attachments: DERBY-2109-02.diff, DERBY-2109-02.stat,
> derby-2109-03-javadoc-see-tags.diff, DERBY-2109-04.diff, DERBY-2109-04.stat,
> DERBY-2109-05and06.diff, DERBY-2109-05and06.stat, DERBY-2109-07.diff,
> DERBY-2109-07.stat, DERBY-2109-08.diff, DERBY-2109-08.stat,
> DERBY-2109-08_addendum.diff, DERBY-2109-08_addendum.stat,
> SystemPrivilegesBehaviour.html, systemPrivs.html, systemPrivs.html,
> systemPrivs.html, systemPrivs.html
>
>
> Add mechanisms for controlling system-level privileges in Derby. See the
> related email discussion at
> http://article.gmane.org/gmane.comp.apache.db.derby.devel/33151.
> The 10.2 GRANT/REVOKE work was a big step forward in making Derby more
> secure in a client/server configuration. I'd like to plug more client/server
> security holes in 10.3. In particular, I'd like to focus on authorization
> issues which the ANSI spec doesn't address.
> Here are the important issues which came out of the email discussion.
> Missing privileges that are above the level of a single database:
> - Create Database
> - Shutdown all databases
> - Shutdown System
> Missing privileges specific to a particular database:
> - Shutdown that Database
> - Encrypt that database
> - Upgrade database
> - Create (in that Database) Java Plugins (currently Functions/Procedures,
> but someday Aggregates and VTIs)
> Note that 10.2 gave us GRANT/REVOKE control over the following
> database-specific issues, via granting execute privilege to system
> procedures:
> Jar Handling
> Backup Routines
> Admin Routines
> Import/Export
> Property Handling
> Check Table
> In addition, since 10.0, the privilege of connecting to a database has been
> controlled by two properties (derby.database.fullAccessUsers and
> derby.database.defaultConnectionMode) as described in the security section of
> the Developer's Guide (see
> http://db.apache.org/derby/docs/10.2/devguide/cdevcsecure865818.html).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
