[
https://issues.apache.org/jira/browse/DERBY-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5376:
-----------------------------
Attachment: DERBY-5376.zip
DERBY-5376.stat
DERBY-5376.diff
Attaching DERBY-5376.diff, DERBY-5376.stat, and DERBY-5376.zip, with changes to
the following files:
M src/adminguide/tadmincbdjhhfd.dita
M src/adminguide/tadminnetservbasic.dita
M src/devguide/cdevcsecure42374.dita
For the two Admin Guide topics, I added information and pointers on
authorization, on top of the existing information on authentication. For the
Dev Guide topic, I added a definition of authorization, and a strong
recommendation to use both authentication and authorization, to the
introductory paragraph (which also appears in the parent topic in the frames
version).
Please let me know what changes are needed and if anything needs to be said
elsewhere. These introductory sections seem to be the best places.
> Documentation should state authentication/authorization requirements more
> strongly
> ----------------------------------------------------------------------------------
>
> Key: DERBY-5376
> URL: https://issues.apache.org/jira/browse/DERBY-5376
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.8.1.2
> Reporter: Kim Haase
> Assignee: Kim Haase
> Attachments: DERBY-5376.diff, DERBY-5376.diff, DERBY-5376.stat,
> DERBY-5376.zip
>
>
> The Administration Guide and Developer's Guide should state more strongly the
> importance of securing a multi-user Derby system by implementing
> authentication and authorization. I have found two Admin Guide topics and one
> Dev Guide topic where this information can most usefully be added.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
