Member since
02-02-2017
31
Posts
2
Kudos Received
0
Solutions
02-22-2017
03:51 AM
Its a two step process and has to be done from Ambari only. Otherwise the changes will not be retained in shiro.ini and it will get overwritten the moment zapplin service is restarted. Any way here are the steps : from ambari Zeppelin > Configs > Advanced zeppelin-env > shiro_ini_content and change the following : A.
[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 maria_dev =<password>, admin #### Add this line #admin = password1, admin #user1 = password2, role1, role2 #user2 = password3, role3 [urls] B. Under URL section make the changes shown below :
[urls] # anon means the access is anonymous. # authcBasic means Basic Auth Security # To enfore security, comment the line below and uncomment the next one #/api/version = anon ## commened this line #/** = anon ##commented this line /** = authc ## uncommented this line Then restart zapplin. try to log in again. This should solve the problem.
... View more
02-03-2017
03:24 PM
@Colin Cunningham
I found that information on the Azure Marketplace page where you deploy the Sandbox. We need to update the tutorial appropriately.
... View more