Theo Sardin created ZEPPELIN-5429:
-------------------------------------
Summary: #{user} config value sometimes resolves to anonymous for
users correctly logged in with LDAP
Key: ZEPPELIN-5429
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5429
Project: Zeppelin
Issue Type: Bug
Components: Kubernetes, zeppelin-interpreter
Affects Versions: 0.9.0
Reporter: Theo Sardin
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:
{code:java}
%spark
sc.getConf.get("user.name") {code}
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 been 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
