You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/23 19:31:20 UTC

[jira] [Commented] (QPID-7279) [Java Broker] with config encryption creating a JDBC VirtualHost fails

    [ https://issues.apache.org/jira/browse/QPID-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390822#comment-15390822 ] 

ASF subversion and git services commented on QPID-7279:
-------------------------------------------------------

Commit 1753882 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1753882 ]

QPID-7279 : Differentiate "recovering" for the first time from an initial config, from real recovery... and in the former case assume any secure fields are unencrypted and thus need to be encrypted and saved after recovery

> [Java Broker] with config encryption creating a JDBC VirtualHost fails
> ----------------------------------------------------------------------
>
>                 Key: QPID-7279
>                 URL: https://issues.apache.org/jira/browse/QPID-7279
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Lorenz Quack
>             Fix For: qpid-java-6.2
>
>
> If configuration encryption is enabled on the broker creating a JDBC VirtualHost via the WMC fails with the following error:
> {{422 - Encrypted value is not valid Base 64 data: 'myPassword'}}
> Also we might not want to log the content of the invalid data due to its potential sensitive nature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org