[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user qinchaofeng commented on the issue: https://github.com/apache/zeppelin/pull/1767 @AhyoungRyu thinks, and the question is I set shiro.ini like this: ![image](https://cloud.githubusercontent.com/assets/17826176/22722126/e429511c-edef-11e6-8b6c-fb0dff957514.png) and set to property zeppelin.anonymous.allowed to true in conf/zeppelin-site.xml I also need to login using username/password --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1767 @qinchaofeng If you want to turn off shiro(login as `anonymous`), you should set `shiro.ini` like below ``` /** = anon #/** = authc ``` --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user qinchaofeng commented on the issue: https://github.com/apache/zeppelin/pull/1767 when I set to property zeppelin.anonymous.allowed to true in conf/zeppelin-site.xml and set cfg in the shiro like this: ![image](https://cloud.githubusercontent.com/assets/17826176/22721945/b0187836-edee-11e6-98be-a71dd5c31de2.png) I also need login using username/password --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1767 @vinayshukla I think what @Leemoonsoo suggested was having only one documentation about this info. And IMO having detailed information to describe about "Authentication in Zeppelin", but it's not good idea put this all contents under "Overview". ![screen shot 2016-12-28 at 11 05 29 am](https://cloud.githubusercontent.com/assets/10060731/21512200/920d3a6a-cced-11e6-816a-8dd3e5f3d255.png) --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user vinayshukla commented on the issue: https://github.com/apache/zeppelin/pull/1767 @Leemoonsoo The CI failure is unrelated, the 2 files changed are template and markdown. Is there a way to re-trigger the CI? --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user bzz commented on the issue: https://github.com/apache/zeppelin/pull/1767 Great improvement, thank you @vinayshukla ! But indeed, it would be really nice to have documentation available on the website as well, as @Leemoonsoo suggests. --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/1767 Thanks @vinayshukla for the contribution. We have a document about configuring shiro authentication on [website](https://github.com/apache/zeppelin/blob/master/docs/security/shiroauthentication.md). What do you think keeping information in the single document(website), instead of keeping two different document for the single feature? --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1767 @vinayshukla Looks good ð --- 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 and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1767: ZEPPELIN-1817 - Added documentation to Zeppelin's shir...
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/1767 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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---