You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2011/06/29 17:09:28 UTC
[jira] [Resolved] (DERBY-5299) Document what you should expect to
see if you enable authentication/authorization on a database which was
created without those safeguards.
[ https://issues.apache.org/jira/browse/DERBY-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas resolved DERBY-5299.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.9.0.0
10.8.1.5
> 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
> Fix For: 10.8.1.5, 10.9.0.0
>
> 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