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] [Closed] (DERBY-5299) Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards.
Date Wed, 29 Jun 2011 15:09:29 GMT

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

Rick Hillegas closed DERBY-5299.
--------------------------------


> 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

        

Mime
View raw message