[
https://issues.apache.org/jira/browse/SPARK-46058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mridul Muralidharan resolved SPARK-46058.
-----------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 43998
[https://github.com/apache/spark/pull/43998]
> [CORE] Add separate flag for privateKeyPassword
> -----------------------------------------------
>
> Key: SPARK-46058
> URL: https://issues.apache.org/jira/browse/SPARK-46058
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 4.0.0
> Reporter: Hasnain Lakhani
> Assignee: Hasnain Lakhani
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Right now with config inheritance we support:
> * JKS with password A, PEM with password B
> * JKS with no password, PEM with password A
> * JKS and PEM with no password
>
> But we do not support the case where JKS has a password and PEM does not. If
> we set keyPassword we will attempt to use it, and cannot set
> `spark.ssl.rpc.keyPassword` to null. So let's make it a separate flag as the
> easiest workaround.
>
> This was noticed while migrating some existing deployments to the RPC SSL
> support where we use openssl support for RPC and use a key with no password
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
