Uploaded image for project: 'Zeppelin'
  1. Zeppelin
  2. ZEPPELIN-5429

#{user} config value sometimes resolves to anonymous for users correctly logged in with LDAP

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.9.0
    • None
    • None

    Description

      Hello zeppelin community,

      (This setup is running on kubernetes).

      We bind a config key "user.name" to "#{user}" value in spark interpreter config.

      The spark interpreter is also in "Per user", "isolated" mode.

      But sometimes even though the user is logged in with LDAP credentials, running:

      %spark
      sc.getConf.get("user.name") 

      We can see it resolves to "anonymous".

      It happens really often and require a global spark interpreter restart (because the whole thing is started as "anonymous").

      I don't have much more information, because we didn't notice any specific pattern to trigger this but it seems that it happens roughly 50% of the time.

      Also, these notes shouldn't even be authorized for anonymous users which makes it weirder.

      We're not sure how to investigate this but I'll be happy to try anything for troubleshooting. 

       

      Thanks & regards,

       

      Theo.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            theosardin Theo Sardin

            Dates

              Created:
              Updated:

              Slack

                Issue deployment