db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5928) Add more task focus to Derby security documentation
Date Mon, 22 Oct 2012 15:10:12 GMT

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

Kim Haase updated DERBY-5928:
-----------------------------

    Attachment: DERBY-5928.zip
                DERBY-5928.stat
                DERBY-5928.diff

Attaching DERBY-5928.diff, DERBY-5928.stat, and DERBY-5928.zip, with the following changes:

M       src/devguide/cdevcsecure12392.dita
M       src/devguide/derbydev.ditamap
M       src/devguide/tdevcsecure81850.dita
A       src/devguide/cdevcsecureidentity.dita
M       src/devguide/tdevcsecure82556.dita
M       src/devguide/cdevcsecuree.dita

Instead of putting all the conceptual material into a catchall topic, I created a new topic
for the "Identity in Derby" material and moved the figures to the "Configuring security in
a client/server environment" and "Configuring security in an embedded environment" topics,
respectively.

I hope I covered all the needed tasks. Please let me know if more work is needed.
                
> Add more task focus to Derby security documentation
> ---------------------------------------------------
>
>                 Key: DERBY-5928
>                 URL: https://issues.apache.org/jira/browse/DERBY-5928
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.9.1.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-5928.diff, DERBY-5928.stat, DERBY-5928.zip
>
>
> It has been recommended that the Derby security documentation in the Developer's Guide
should have more of a task-based focus: instead of beginning with an outline of security concepts
and then describing the tasks a user or administrator should perform to secure Derby, we should
begin with a list of the steps required for security, with links to details on how to perform
them, and cover the concepts after that. Users should have a single location where they can
verify that they have done everything they can to ensure database security.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message