db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5299) Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards.
Date Tue, 28 Jun 2011 16:12:17 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-5299:
---------------------------------

    Attachment: derby-5299-01-aa-securingOldDatabase.tar
                derby-5299-01-aa-securingOldDatabase.diff

Attaching a derby-5299-01-aa-securingOldDatabase.diff patch and corresponding tarball of generated
html pages: derby-5299-01-aa-securingOldDatabase.tar. This patch adds a new section to the
Developer's Guide, nested under the existing "Setting the SQL standard authorization mode"
topic. The new section is titled "Upgrading an old database to use SQL standard authorization".
The new section explains how to enable authentication and SQL authorization on an old, unsecured
database. The new section also lists some behavioral differences which you will notice after
upgrading your database this way.

Touches the following files:

M      src/devguide/derbydev.ditamap
A      src/devguide/cdevcsecuresqlauthupgrade.dita


> 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
>
>
> 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

        

Mime
View raw message