Configure Zeppelin for Authentication: Non-Production Use
This section describes how to configure Apache Zeppelin quickly for non-production use.
The following steps provide a quick, basic form of authentication. This approach is not for production use; usernames and passwords are exposed in clear text. For production use, you should use LDAP or Active Directory as the identity source.
To configure authentication for informal use or testing:
Populate the [urls] section as follows:
authcas the authentication method in the URL section of
shiro.inicontents, and make sure that the
authcline is not commented out.
- To disable anonymous access to Zeppelin, add a comment character
#) at the start of the line containing
/** = anon.
Here is an example:
[urls] #/api/version = anon #/** = anon /** = authc
[users]section as follows:
Specify authorized accounts and associated passwords in
shiro_inisettings: for clusters managed by Ambari, update
shiro_ini_content; for non-Ambari clusters, update the
The following example configures authentication for users
user2, with passwords
[users] admin = password1 user1 = password2 user2 = password3
- Restart the Zeppelin server using Ambari.
- After completing these steps, Zeppelin requires authentication of user credentials before allowing access to the Zeppelin UI.