Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 54239 invoked from network); 21 Feb 2007 23:29:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2007 23:29:28 -0000 Received: (qmail 26328 invoked by uid 500); 21 Feb 2007 23:29:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 26297 invoked by uid 500); 21 Feb 2007 23:29:35 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 26288 invoked by uid 99); 21 Feb 2007 23:29:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2007 15:29:35 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2007 15:29:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9A1467141A3 for ; Wed, 21 Feb 2007 15:29:06 -0800 (PST) Message-ID: <20786888.1172100546628.JavaMail.jira@brutus> Date: Wed, 21 Feb 2007 15:29:06 -0800 (PST) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2361) Documentation should give examples for using the different security mechanisms In-Reply-To: <16325213.1172000825524.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474871 ] Kim Haase commented on DERBY-2361: ---------------------------------- Thanks for clarifying that, Andrew. I realized I'll also need to create a new topic in the Reference Manual for the securityMechanism attribute, under "Setting attributes for the database connection URL". I think the details on the attribute, along with an example, can go there, with a cross-reference to it from cadminapps49914. Also, on a slightly different subject, one of the topics under cadminapps49914 is "Enabling the encrypted user ID and password security mechanism". It says that in order to use this mechanism you need "IBM JCE (Java Cryptography Extension) 1.2.1 or later", but it doesn't say how to get this if you don't already have it. Should this be a separate JIRA issue? > Documentation should give examples for using the different security mechanisms > ------------------------------------------------------------------------------ > > Key: DERBY-2361 > URL: https://issues.apache.org/jira/browse/DERBY-2361 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.2.2.0 > Reporter: Andrew McIntyre > Assigned To: Kim Haase > > The Derby Server and Administration guide talks about the different security mechanisms, but does not give examples of how these can be used via connection URLs, it only mentions the client DataSource field names. > http://db.apache.org/derby/docs/10.2/adminguide/cadminapps49914.html > The documentation should give examples of how to use the different security mechanisms via connection URLs, and perhaps an example of how the client field names would be used programmatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.