Hi Moon, Yes, no problem. I edited zeppelin-site.xml as follows:
<property> <name>zeppelin.server.addr</name> <value>localhost</value> <description>Server address</description> </property> ... <property> <name>zeppelin.anonymous.allowed</name> <value>false</value> <description>Anonymous user allowed by default</description> </property> And my shiro.ini file looks like this: # # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # [users] # List of users with their password allowed to access Zeppelin. # To use a different strategy (LDAP / Database / ...) check the shiro doc at http://shiro.apache.org/configuration.html#Configuration-INISections admin = password1 user1 = password2, role1, role2 user2 = password3, role3 user3 = password4, role2 # Sample LDAP configuration, for user Authentication, currently tested for single Realm [main] #ldapRealm = org.apache.shiro.realm.ldap.JndiLdapRealm #ldapRealm.userDnTemplate = cn={0},cn=engg,ou=testdomain,dc=testdomain,dc=com #ldapRealm.contextFactory.url = ldap://ldaphost:389 #ldapRealm.contextFactory.authenticationMechanism = SIMPLE [urls] # anon means the access is anonymous. # authcBasic means Basic Auth Security # To enfore security, comment the line below and uncomment the next one #/** = anon /** = authcBasic Also, here is a screenshot of what my Zeppelin site's home screen looks like: http://pasteboard.co/2qLfOO0y.png Thanks, Peter > On 18 Mar 2016, at 17:54, moon soo Lee <m...@apache.org> wrote: > > Hi Peter, > > There're no special flag for maven build process. > Could you share how you modified your shiro.ini? > > Thanks, > moon > > On Fri, Mar 18, 2016 at 2:45 AM Peter Briggs <peter.bri...@heystaks.com > <mailto:peter.bri...@heystaks.com>> wrote: > Hi Moon, > > Thanks for the reply. Yes, I tried cleaning the cache, and I also get the > same result in Chrome incognito mode. > > I wonder is there some option that I need to add as part of the maven build > process to enable auth? I just built zeppelin with the defaults and then > followed the instructions for enabling authentication in the shiro.ini and > zeppelin-site.xml config files. > > Thanks, > Peter > >> On 17 Mar 2016, at 23:03, moon soo Lee <m...@apache.org >> <mailto:m...@apache.org>> wrote: >> >> Hi Peter, >> >> Thanks sharing the problem. That seems unusual. Have you tried clean browser >> cache? >> >> Thanks, >> moon >> >> On Tue, Mar 15, 2016 at 3:48 PM Peter Briggs <peter.bri...@heystaks.com >> <mailto:peter.bri...@heystaks.com>> wrote: >> Hi, >> >> I am having trouble getting the Shiro user authentication to work for >> Zeppelin - the issue is that when I open the Zeppelin home page in browser, >> the login dialog does not appear as expected. I’ve tested in Chrome and >> Safari, which the same results. >> >> I downloaded the latest 0.6.0-incubating-SNAPSHOT, and followed the config >> instructions here: >> https://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/manual/shiroauthentication.html >> >> <https://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/manual/shiroauthentication.html> >> >> >> The config setting that disables anonymous access seems to work ok though, >> as I can’t access any notebooks on the site when I apply those settings. The >> DEBUG logs seem to confirm that the shiro.ini file has been found and used >> for configuration. And the logs also show that my requests to the site are >> considered anonymous, which is to be expected given I haven’t logged in yet. >> >> Anyone have any ideas where I might be going wrong? >> >> Thanks, >> Peter >
