GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/711
[Zeppelin-661] Add a documentation for Shiro authentication
### What is this PR for?
About a month ago, Shiro authentication for Zeppelin is merged by #586.
Even though we already have
[SECURITY-README.md](https://github.com/apache/incubator-zeppelin/blob/master/SECURITY-README.md),
many people do not know about the existence of this file. So I wrote a docs to
the Zeppelin documentation website, based on `SECURITY-README.md` to guide step
by step for Zeppelin users.
### What type of PR is it?
Documentation
### Todos
* [x] - Add shiro authentication docs
* [x] - Add **zeppelin.anonymous.allowed** property in `zeppelin-site.md`
* [x] - Indent **Websocket security** section in `SECURITY-README.md`
### Is there a relevant Jira issue?
[ZEPPELIN-661](https://issues.apache.org/jira/browse/ZEPPELIN-661)
### How should this be tested?
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/incubator-zeppelin ZEPPELIN-661
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/711.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #711
----
commit d841a8a23c3d8765bb8a4f7224c9b8a91d642499
Author: Ryu Ah young <fbdkdu...@hanmail.net>
Date: 2016-02-12T02:16:14Z
ZEPPELIN-661: Add shiro authentication docs
commit f050f8de76044d0d3d5b119bcc0004c95b26f9e6
Author: Ryu Ah young <fbdkdu...@hanmail.net>
Date: 2016-02-12T02:18:00Z
ZEPPELIN-661: Add 'zeppelin.anonymous.allowed' property in
zeppelin-site.xml to install.md
commit 795f177163c61a370a0dd0f6aae00b408f801909
Author: Ryu Ah young <fbdkdu...@hanmail.net>
Date: 2016-02-12T02:19:26Z
ZEPPELIN-661: indent 'Websocket security' section in SECURITY-README.md
----
---
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.
---
