Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 8 May 2013 17:05:15 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12646654.1368032631844.288288.1368032715430@arcas>
In-Reply-To: <JIRA.12646654.1368032631844@arcas>
References: <JIRA.12646654.1368032631844@arcas>
Subject: [jira] [Created] (DERBY-6217) Put all of the security documentation
 in a single, separate user guide
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rick Hillegas created DERBY-6217:
------------------------------------

             Summary: Put all of the security documentation in a single, separate user guide
                 Key: DERBY-6217
                 URL: https://issues.apache.org/jira/browse/DERBY-6217
             Project: Derby
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 10.11.0.0
            Reporter: Rick Hillegas


Right now the security documentation is divided among our user guides. This makes is hard for customers to understand Derby's defenses and how to configure all relevant security mechanisms for an application. As demonstrated by the discussion on DERBY-6160, some security mechanisms involve multiple Derby jar files and multiple application tiers. Material for these mechanisms is scattered across the existing user guides. It would be less confusing if all of Derby's security documentation were separated out into a new Security Guide.

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