Keystore in secret corrupted after editing the secret in the OpenShift Container Platform 4 - Management Console

Solution Verified - Updated -

Issue

  • Storing a trustore (i.e. truststore.p12) as secret in Openshift is working fine as long as the secret is not edited. As soon as any field from the secret is changed over the GUI the file gets correupted and the application receives an exception like:

    java.io.IOException: Invalid keystore format.
    
  • When modifying a secret in the Management Console that has a binary file inclued (such as a keystore), the keystore will get corrupted post the modification and therefore impact application functionality.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content