Mailing-List: contact commits-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openejb.apache.org
Message-ID: <296199172.1255125391268.JavaMail.jira@brutus>
Date: Fri, 9 Oct 2009 14:56:31 -0700 (PDT)
From: "Jean-Louis MONTEIRO (JIRA)" <jira@apache.org>
To: commits@openejb.apache.org
Subject: [jira] Commented: (OPENEJB-1076) Allow datasource passwords to be
 ciphered
In-Reply-To: <1222896579.1253868855990.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/OPENEJB-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764220#action_12764220 ] 

Jean-Louis MONTEIRO commented on OPENEJB-1076:
----------------------------------------------

Thanks David for the hint.
I finally got a shoot to that and use a file under META-INF/org.apache.openejb.resource.jdbc.PasswordCodec to specify the codec implementation.

    Transmitting file data ...
    Committed revision 823709.

> Allow datasource passwords to be ciphered
> -----------------------------------------
>
>                 Key: OPENEJB-1076
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1076
>             Project: OpenEJB
>          Issue Type: New Feature
>         Environment: All
>            Reporter: Jean-Louis MONTEIRO
>            Assignee: Jean-Louis MONTEIRO
>             Fix For: 3.1.2
>
>
> OpenEJB supports plain text passwords in datasource definition (openejb.xml).
> Nowadays, security is more and more important that's why it would be nice to enhance datasources configuration to support ciphered passwords. 
> By the way, this feature must be extensible to allow end users to define their own algorithm if needed.

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