moon wrote
> Do you mean sensitive information inside of paragraph code or output?
Code in particular. I've seen some users do this with system properties, but
it would be very useful to have something in that is more dynamic and is
bound to the notebook.
moon wrote
> Zeppelin itself does not have any special treatment of such contents.
> If your viewers does not run notebook, then those sensitive informations
> can packaged into jar and loaded, referenced, like
>
> createConnection(com.mycompany.secret.SensitiveInformation.getPassword())
>
> instead of doing
>
> createConnection("plain text password")
That works for the %spark interpreter, but what about others such as %r,
%jdbc, etc.? What would be really nice is something like Ansible Vault
<http://docs.ansible.com/ansible/playbooks_vault.html> but for notebook
properties. Then these sensitive pieces of information could be encrypted in
the notebook and unlocked by notebook authors. The system could decrypt
properties using a notebook password. Heck, could even extend this concept
to the entire paragraph text or notebook level as well.
--
View this message in context:
http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Protecting-sensitive-paragraph-information-tp2362p2378.html
Sent from the Apache Zeppelin Users (incubating) mailing list mailing list
archive at Nabble.com.
