[
https://issues.apache.org/jira/browse/SOLR-11690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268988#comment-16268988
]
Erick Erickson commented on SOLR-11690:
---------------------------------------
I took a quick look (note that I know nothing about this code). But chopping
the last character off the password prior to decoding seems unlikely to be a
general solution. That code hasn't been changed in over 2 years, I'd expect
others would have run in to this and reported it in the intervening time.
Are you absolutely sure you haven't somehow added an extra character somehow?
Have you tried a new password fresh to see if the problem persists or is some
user error? Is there any chance you have some binary/text copying issue?
> DIH JdbcDataSource - Problem decoding encrypted password using encryptKeyFile
> -----------------------------------------------------------------------------
>
> Key: SOLR-11690
> URL: https://issues.apache.org/jira/browse/SOLR-11690
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - DataImportHandler
> Affects Versions: 6.6.2
> Reporter: Rajesh Arumugam
> Labels: easyfix
>
> The password decryption is not working fine because of a bug in
> JdbcDataSorce.java -> decryptPwd(Context context, Properties initProps)
> method. The problem is due to bad construction of key string while making a
> call to CryptoKeys.decodeAES(). Due to this the CryptoKeys throws "*Bad
> password, algorithm, mode or padding; no salt, wrong number of iterations or
> corrupted ciphertext.*" exception while trying to decode password.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
