Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 29 Jun 2011 14:20:28 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2097275717.2548.1309357228453.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <553006576.44225.1309192007707.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5299) Document what you should expect to
 see if you enable authentication/authorization on a database which was
 created without those safeguards.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen commented on DERBY-5299:
-------------------------------------------

Thanks, Rick. The updated patch looks good.

> Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5299
>                 URL: https://issues.apache.org/jira/browse/DERBY-5299
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: 5299_setup.sql, 5299_withAuth.sql, derby-5299-01-aa-securingOldDatabase.diff, derby-5299-01-aa-securingOldDatabase.tar, derby-5299-01-ab-securingOldDatabase.diff, derby-5299-01-ab-securingOldDatabase.tar
>
>
> It is possible to deploy the first version of your Derby-powered application without enabling authentication and authorization. In a later version of your application, you may want to boost security by enabling these features. It would be good to tell users what they should expect when they enable authentication/authorization on a legacy database.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira