Details

    Description

      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

      Attachments

        Activity

          Issue resolved by pull request 43998
          https://github.com/apache/spark/pull/43998

          mridulm80 Mridul Muralidharan added a comment - Issue resolved by pull request 43998 https://github.com/apache/spark/pull/43998

          People

            hasnain-db Hasnain Lakhani Assign to me
            hasnain-db Hasnain Lakhani
            Votes:
            0 Vote for this issue
            Watchers:
            Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Error getting Slack data from Jira

                Issue deployment

                  Client must be authenticated to access this resource.