You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Ankur SAINI (Jira)" <ji...@apache.org> on 2025/07/12 05:06:00 UTC

[jira] [Created] (ZEPPELIN-6231) Authentication to the custom repository fails after the Zeppelin server is restarted.

Ankur SAINI created ZEPPELIN-6231:
-------------------------------------

             Summary: Authentication to the custom repository fails after the Zeppelin server is restarted.
                 Key: ZEPPELIN-6231
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6231
             Project: Zeppelin
          Issue Type: Bug
          Components: zeppelin-server
    Affects Versions: 0.12.0
            Reporter: Ankur SAINI


Hello,



We are deploying Zeppelin on Kubernetes. When we configure a custom Maven repository with authentication, everything works correctly initially. However, after restarting the Zeppelin server, the interpreter settings are reloaded from {{{}interpreter.json{}}}, and the connection to the custom repository fails due to incorrect or missing credentials.

 

After extensive troubleshooting, we found that the issue occurs because the password for the custom Maven repository is stored in an object of the {{SecretAuthentication}} class (from {{{}maven-resolver-util.jar{}}}), which encrypts the password upon assignment. When Zeppelin serializes the {{InterpreterInfoSaving}} object, this encrypted password is saved to the {{interpreter.json}} file.

However, upon restarting the Zeppelin server, the file is reloaded, and the encrypted password cannot be decrypted. This happens due to the presence of static objects in the {{SecretAuthentication}} class, resulting in failed authentication to the custom repository.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)