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] Commented: (DERBY-2466) Allow dynamic reloading of the security policy file
Date Fri, 23 Mar 2007 19:48:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483723

Rick Hillegas commented on DERBY-2466:

I can separate (1) from (2) and create a different template file. As we add new Derby permissions,
we will have to remember to add them to both files.

In the interests of not muddying this initial patch, I propose to make these changes in follow-on

1) Create the new template file.

2) Adjust the release-build scripts so that the template policy rather than the Basic policy
is copied to demo/templates/server.policy

3) Make appropriate changes to the Secure Server spec (DERBY-2196) and System Privileges (DERBY-2109)

4) Adjust the user guides to reflect the separation of (1) from (2).

> Allow dynamic reloading of the security policy file
> ---------------------------------------------------
>                 Key: DERBY-2466
>                 URL: https://issues.apache.org/jira/browse/DERBY-2466
>             Project: Derby
>          Issue Type: New Feature
>          Components: Security
>            Reporter: Rick Hillegas
>         Assigned To: Rick Hillegas
>             Fix For:
>         Attachments: derby-2466-01.diff
> The spec attached to DERBY-2109 describes how to allow the policy file to be dynamically
reloaded while a server is running: We add a getPolicy permission to the Basic policy and
we add a DBA-owned system procedure, SYSCS_UTIL.SYSCS_REFRESH_SECURITY_POLICY(), which reloads
the policy file. This JIRA tracks that work.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message