db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5522) Document the NATIVE authentication scheme.
Date Mon, 12 Mar 2012 17:23:37 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227706#comment-13227706

Rick Hillegas commented on DERBY-5522:

Thanks, Kim, for running these additional experiments and for attaching the latest version
of the test program.

>I find that now that defaultConnectionMode is not set, if I try to log in to the database
as a user who has no assigned role, I can do it. What are the default privileges for a user?
Everything, apparently? 

The Reference Guide says that fullAccess is the default value of derby.database.defaultConnectionMode.

>Also, when I log in as a user whose role was granted only SELECT privileges on a table,
I find that I can create the table all over again. 

Maybe the confusion arises because user GUEST is creating a table named ACCESSIBLETBL? That
table is being created in the GUEST schema and is different from SYSADMIN.ACCESSIBLETBL, the
table which is the object of the GRANT statements.

> Document the NATIVE authentication scheme.
> ------------------------------------------
>                 Key: DERBY-5522
>                 URL: https://issues.apache.org/jira/browse/DERBY-5522
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java,
NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java
> We should document NATIVE authentication after we have implemented the changes described
on DERBY-866. The documentation changes are described by the functional spec UserManagement.html
attached to that issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message