Github user BigDataDataAnalyst commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@AhyoungRyu
I am facing the same issue with Zeppelin.
Here is the JIRA ticket link
https://issues.apache.org/jira/browse/ZEPPELIN-3133
It would be great if
Github user RoxanaTapia commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@AhyoungRyu Can somebody have a look in the ticket? I was wondering if
changing the role value to something else would help, until now all of them are
* (e.g. admin = *, user= *) can I gran
Github user RoxanaTapia commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@AhyoungRyu Thanks for the quick response, here is the JIRA ticket link
https://issues.apache.org/jira/browse/ZEPPELIN-3133
---
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@RoxanaTapia Could you file a Jira issue here
https://issues.apache.org/jira/projects/ZEPPELIN so that it can be tracked &
handled separately ? Once a patch is merged, can't be opened again or
Github user RoxanaTapia commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Hi,
I'm experiencing this issue but with shiro activated. I want the "Note
Permissions" button to be activated only for authorized users (e.g. admins).
Right now any user can access,
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1694
After this patch, if i turn off shiro and load any notebook (without click
permission button)
browser console print 403 forbidden,
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Will merge this into master if there are no more comments!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@prabhjyotsingh Thanks! :D
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Tested, works as expectation. LGTM!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Can someone review this one? ð
ð¼
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
CI is all green now! Ready to review.
Here are some brief summaries what I did.
Since from this PR `anonymous`(non authenticated) user can't set note
permission, related test
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@prabhjyotsingh @cloverhearts @astroshim Sorry for my late response.
I added checking anonymous user \w notebook rest api. So if anonymous users
try to click lock icon / `GET` note
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@prabhjyotsingh @cloverhearts @astroshim Sorry for my late response.
I added checking anonymous user by using websocket and updated PR
description \w new UI screenshot image. Please take a
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1694
I agree with @prabhjyotsingh and @cloverhearts blocking to change the
permission on a backend side too.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1694
@prabhjyotsingh @cloverhearts Didn't think about that way. It makes sense.
Thanks for your suggestion. Let me update then :)
---
If your project is set up for it, you can reply to this email
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1694
It is a cool feature.
I would like to say one thing.
If you need to prevent configuration changes for anonymous users,
you should not modify them only in the Web UI.
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Haven't tried it yet, but IMO we should have a check at backned for the
same (both API and websocket).
---
If your project is set up for it, you can reply to this email and have your
Github user prabhu-pictink commented on the issue:
https://github.com/apache/zeppelin/pull/1694
Haven't tried it yet, but I think we should have a check at backned for the
same (both API and websocket).
---
If your project is set up for it, you can reply to this email and have your
18 matches
Mail list logo
