Created 02-03-2017 05:42 PM
Hi. I have started a HDP Sandbox 2.5.0 in Azure. I see that current sandbox has issue in that Zeppelin is not accessible from Abari Views. I can get to Zeppelin via port 9995 in browser but it has me as anonymous. How can I switch to being user maria_dev and interact w/ my sandbox.hortonworks.com build in Zeppelin?
Thanks. - Colin
p.s. I was unsuccessfully trying to move my way thru the tutorial here, https://github.com/hortonworks/tutorials/blob/hdp-2.5/tutorials/hortonworks/getting-started-with-apa....
Created 02-03-2017 05:47 PM
By default zeppelin is configured with anonymous authentcation. You must set [url] section in shiro_ini of zeppelin service as below. And without AD/LDAP authencation you can set the usernames in [users]. After this changes restart zeppelin services. Now with /api/anon commented you must login with user name set in [users]
[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] # This section is used for url-based security. # You can secure interpreter, configuration and credential information by urls. Comment or uncomment the below urls that you want to hide. # anon means the access is anonymous. # authc means Form based Auth Security # To enfore security, comment the line below and uncomment the next one /api/version = anon #/** = anon ###Comment anon /** = authc ####Add this line
Created 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.
B. Under URL section make the changes shown below :
Then restart zapplin. try to log in again. This should solve the problem.