[
https://issues.apache.org/jira/browse/QPID-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299889#comment-15299889
]
Lorenz Quack commented on QPID-7279:
------------------------------------
Initially I thought this is related to the attribute being marked as secure
(and thus not only limited to JDBC VHs) but oddly creating a User which also
has a password field marked as secure succeeds.
I suspect that either they are somehow handled differently or the root cause is
a different one.
Further investigation needs to be conducted to find out the full scope of this
issue.
> [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
>
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
