Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <3331847.1172010425517.JavaMail.jira@brutus>
Date: Tue, 20 Feb 2007 14:27:05 -0800 (PST)
From: "Andrew McIntyre (JIRA)" <jira@apache.org>
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


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

Andrew McIntyre commented on DERBY-2361:
----------------------------------------

The Strong Substitute Password is securityMechanism number 8, so:

jdbc:derby://localhost/mydb;user=myuser;password=mypassword;securityMechanism=8

for the encrypted username and password, the number is 9, so:

jdbc:derby://localhost/mydb;user=myuser;password=mypassword;securityMechanism=9

I believe that you can also set a default security mechanism for a server by setting the property derby.drda.securityMechanism to one of those values to ensure that clients can only connect if they are using a specific security mechanism, and that also needs documentation, see DERBY-928. That could be separated out to a separate issue if desired, though.

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