I have not tried using Shiro with Zeppelin yet, but one thing I'll point
out is that for Zeppelin on EMR, configuration should be done through
zeppelin-env.sh rather than zeppelin-site.xml. All Zeppelin configuration
properties can be set via either file, so we (I'm on the EMR team, btw)
decided to support just one of them. At least, zeppelin-env.sh is the only
one you can change via the Configuration JSON you may supply when creating
a cluster. Nothing stops you from ssh'ing to the master node and changing
the files yourself.

~ Jonathan
On Fri, May 26, 2017 at 6:15 PM Jaideep Singh <jaideep...@gmail.com> wrote:

> Hello,
>
> I am also new to this but you can try changing
> > /api/version = authc,roles[admin]
>
> Thanks,
> Jaideep Singh
>
>
>
>
> On Saturday, May 27, 2017, kebarcla <kbarc...@ancestry.com> wrote:
>
>> Hello,
>>
>> I'm running Zep 0.7.1 on the new EMR 5.5 on AWS: I have all the usual big
>> data tools deployed. I'd like to set up users to access the cluster.
>>
>> In following the steps documented in 'Apache Shiro authentication for
>> Apache
>> Zeppelin' I'm finding that my changes to conf/shiro.ini or
>> zeppelin-site.xml
>> on the master node seem to be ignored: I don't see them under
>> 'Configuration' on the user drop-down.
>>
>> After restarting Zeppelin server, I'm still automatically logged in as
>> 'anonymous.'
>> How does one log out, and log back in as another user?
>> How to get Zeppelin server to recognize config file changes?
>>
>> Thanks for any pointers,
>> Ken
>>
>> # shiro.ini changes:
>>
>> < newuser = Password!, admin
>> < #/api/version = anon
>> < /api/interpreter/** = authc, roles[admin]
>> < /api/configurations/** = authc, roles[admin]
>> < /api/credential/** = authc, roles[admin]
>> ---
>> > /api/version = anon
>> > #/api/interpreter/** = authc, roles[admin]
>> > #/api/configurations/** = authc, roles[admin]
>> > #/api/credential/** = authc, roles[admin]
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Zeppelin-0-7-1-config-file-not-being-read-tp5695.html
>> Sent from the Apache Zeppelin Users (incubating) mailing list mailing
>> list archive at Nabble.com.
>>
>

Reply via email to