Hey all -

On file system based storage plugins, security is straight forward with
filesystem permissions etc.  How do we secure storage plugins?  It would
seem we would want a situation where people could not access certain
storage plugins especially since authentication to the source system is
going to be "wide open" (i.e. there is no pass through auth to a backend
Mongo server, JDBC system, or Hbase setup)  thus how do we wrap security
around these?

Even basic security... i.e. only X user can use them, so we can use them to
load parquet tables or something where we can apply security.

Thoughts?

John

Reply via email to