[ZEPPELIN-5429] #{user} config value sometimes resolves to anonymous for users correctly logged in with LDAP

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.0
• Component/s: Kubernetes, zeppelin-interpreter
• Assignee: Unassigned
• Reporter: Theo Sardin
• Created: 24/Jun/21 03:58
• Updated: 14/Jul/21 01:52

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.