Good suggestion. We also need LDAP authentication.
> On Nov 9, 2015, at 12:46 AM, Jeff Steinmetz <jeffrey.steinm...@gmail.com> > wrote: > > If there is enough interest and developers are into the idea: a pluggable > auth mechanism would be something to think about. Then the auth system could > use existing Json Web Tokens (single sign on), JWT via Auth0, Stormpath, > custom user:password with bcrypt passwords in a database, simple > authentication with a shared user:password, etc. > > Jeff > > > From: Girish Reddy > Reply-To: <users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>> > Date: Saturday, November 7, 2015 at 10:35 PM > To: <users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>> > Subject: Re: authentication > > Thank you for the suggestion. What do you think of writing a custom auth > module that gets executed on NotebookServer "onOpen" method or "checkOrigin" > methods? I can then restrict unauthorized users from accessing the > notebooks. Thoughts please? > > > > On Tue, Nov 3, 2015 at 8:17 AM, moon soo Lee <m...@apache.org > <mailto:m...@apache.org>> wrote: >> Hi, >> >> Currently, Zeppelin does not have authentication. >> But you can try nice on going work here >> https://github.com/apache/incubator-zeppelin/pull/53 >> <https://github.com/apache/incubator-zeppelin/pull/53> >> Alternatively, you can use any http proxy in front of Zeppelin for >> authentication. >> >> Thanks, >> moon >> >> >> On Tue, Nov 3, 2015 at 4:54 PM Girish Reddy <gir...@springml.com >> <mailto:gir...@springml.com>> wrote: >>> Hello: >>> >>> What are the options if we wish to secure notebooks with user >>> authentication? >>> >>> Thanks. >
