db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2109) System privileges
Date Thu, 11 Jan 2007 16:28:27 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463931

Daniel John Debrunner commented on DERBY-2109:

The functional spec says:
We add a new method to Derby's org.apache.derby.authentication.UserAuthenticator interface.
This expands Derby's pluggable authentication logic to allow the customer to map authenticationIDs
to custom Principals:

    public Principal getPrincipal( String userName ) throws SQLException;

I've been thinking more about this call.

Investigating how Principles are used, e.g. in the Subject class, a Subject (which is the
object passed to doAsPrivileged) can contain more than one Principle. Thus to me it seems
the getPrinciple() should have the flexiblity to return any number of Principles, so the return
type should be a Set (see Subject) and thus can contain zero or more Principles. This then
starts to get into the ability to support roles, e.g. an implementation could return three
   DatabasePrincipal("SYSTEM ADMIN"}

and then this allows indirection between a specific user and a role.

Then thinking about implementing this interface I think  the proposed api has two issues:

  - if the authentication information is stored elsewhere (e.g. ldap) then getPrinciple()
cannot work since no password is available
  - it requires a double trip to the authentication store (e.g. two ldap calls)

Thus it seems to me the api should really be:

 	public Set authenticateUserWithPrinciples(String userName,
								 String userPassword,
								 String databaseName,
								 Properties info

     or (I think I prefer this one)

        // passing in a DatabasePrinciple, implementations can choose to included in the returned
set or not.
 	public Set authenticateUser(DatabasePrinciple user,
								 String userPassword,
								 String databaseName,
								 Properties info

The maybe if the authenticateUser() that returns a Set returns null the existing old method
is used.

Related to this, the functional spec does not specify what the Principle will be with the
two builtin authentication schemes, BUILTIN and LDAP.
I assume for BUILTIN it will be DatabasePrinciple with the user's identifier, but what should
it be with LDAP? Is there a standard Principle (e..g X500Principle) returned though the api
we use to perform LDAP lookups?


> System privileges
> -----------------
>                 Key: DERBY-2109
>                 URL: https://issues.apache.org/jira/browse/DERBY-2109
>             Project: Derby
>          Issue Type: New Feature
>          Components: Security
>    Affects Versions:
>            Reporter: Rick Hillegas
>             Fix For:
>         Attachments: 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.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message