Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 9 Mar 2012 20:38:59 +0000 (UTC)
From: "Kim Haase (Commented) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1453628390.45354.1331325539837.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <492610270.45752.1323182980210.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5522) Document the NATIVE authentication
 scheme.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kim Haase commented on DERBY-5522:
----------------------------------

Thanks for that clarification about requireAuthentication and sqlAuthorization, Rick. 

I'm moving on to creating a dedicated credentials database using derby.properties. It worked fine. When I created the credentials DB and added some users, I also set the default connection mode to noAccess and specified some users as full access and others as read only access. Would this be customary when you create the database? 

                
> 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: 10.9.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: 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